feat: default to servers directory for new projects

[eaandersen]

Default to servers directory for new projects

Motivation and Context

This change improves project organization by defaulting new MCP servers to a dedicated servers directory. This helps maintain a clean workspace structure when dealing with multiple MCP server projects.

How Has This Been Tested?

• Created new project without --path (verifies default to servers directory)
• Created new project with --path override (verifies option still works)
• Created multiple projects in sequence (verifies directory handling)
• Tested on Windows environment

Breaking Changes

None. This is a non-breaking change as:

• Existing --path functionality remains unchanged
• Only affects default behavior when no path is specified

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

This change is part of a larger effort to improve workspace organization for projects that will manage multiple MCP servers. The servers directory convention makes it easier to:

• Organize multiple server projects
• Apply workspace-wide tooling
• Maintain consistent structure across teams