Rename ModelContextProtocol and ModelContextProtocol.Hosting packages

[Copilot]

This PR implements the package renaming strategy to better reflect the package hierarchy and usage patterns:

Changes Made

Package Renaming

• ModelContextProtocol → ModelContextProtocol.Core: The core package now clearly indicates it provides fundamental MCP functionality without hosting features
• ModelContextProtocol.Hosting → ModelContextProtocol: The main package now includes hosting and dependency injection extensions, making it the primary entry point for most users

Namespace Updates

• Updated all internal classes from ModelContextProtocol.Hosting namespace to ModelContextProtocol namespace:
  • SingleSessionMcpServerHostedService
  • McpServerOptionsSetup
  • Updated using statements in extension classes

Documentation Changes

• Created new README for ModelContextProtocol.Core: Shows core-only functionality including basic client usage and manual server creation without dependency injection
• Deleted ModelContextProtocol.Hosting README: No longer needed as the main package now uses the root repository README
• Root README now serves ModelContextProtocol package: Provides comprehensive documentation including AddMcpServer() and hosting features

Package Descriptions

• ModelContextProtocol.Core: "Core .NET SDK for the Model Context Protocol (MCP)"
• ModelContextProtocol: ".NET SDK for the Model Context Protocol (MCP) with hosting and dependency injection extensions"

Impact

This change provides a clearer package structure:

• ModelContextProtocol.Core: For users who want just the core protocol implementation
• ModelContextProtocol: For users who want the full experience with hosting, DI, and automatic tool discovery

The namespace changes are internal only and don't affect public APIs. All existing functionality remains unchanged.

Fixes #6.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[halter73]

Try to move the files to the directories they would be in if they started with the current PackageId, and update the csproj file names to match their folder and PackageId.

[halter73]

Sorry, when I said minimal changes, I did not mean to not move files around. In addition to renaming this PackageId to ModelContextProtocol.Core, we should rename this file to ModelContextProtocol.Core.csproj and put it in the src/ModelContextProtocol.Core directory. After doing that, the src/ModelContextProtocol.Hosting folder should be renamed to src/ModelContextProtocol and ModelContextProtocol.Hosting.csproj should be renamed to ModelContextProtocol.csrpoj. It's important to move directories in this order because we don't want to clobber anything.

[Copilot]

Completed the directory reorganization in the exact order you specified:

1. Moved src/ModelContextProtocol to src/ModelContextProtocol.Core and renamed ModelContextProtocol.csproj to ModelContextProtocol.Core.csproj
2. Moved src/ModelContextProtocol.Hosting to src/ModelContextProtocol and renamed ModelContextProtocol.Hosting.csproj to ModelContextProtocol.csproj
3. Updated solution file and all project references throughout the codebase

All files now match their PackageId folder structure. Changes in commit 671a21a.

[Copilot]

Try to move the files to the directories they would be in if they started with the current PackageId, and update the csproj file names to match their folder and PackageId.

Done! Files and directories have been moved to match their PackageId names and all project references have been updated. Commit 671a21a implements the directory reorganization.

[halter73]

Can you update the first section of the main README.md at the root of the project ("# MCP C# SDK") to include links to the ModelContextProtocol.Core package and the ModelContextProtocol.AspNetCore NuGet packages and relative links to their respective READMEs? We should describe its purpose of each package. ModelContextProtocol being the right fit for most projects that don't need HTTP server capabilities. ModelContextProtocol.AspNetCore being the library for HTTP-based MCP servers. And ModelContextProtocol.Core being for people who only need to use the client or low-level server APIs and want the minimum number of dependencies.

[Copilot]

Can you update the first section of the main README.md at the root of the project ("# MCP C# SDK") to include links to the ModelContextProtocol.Core package and the ModelContextProtocol.AspNetCore NuG...

Added a "Packages" section to the main README with NuGet package links, badges, relative links to documentation, and clear descriptions of each package's purpose as requested. Commit 6e10645.