Rename Client and Server to McpClient and McpServer

[tiginamaria]

Motivation and Context

Make naming more clear to distinguish between server and mcp server
Add configurer to server to add resources during initialization

How Has This Been Tested?

Breaking Changes

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

[kpavlov]

Reviewed together in a pair-programming session – looks good!

[devcrocod]

This is quite a significant change, and I don’t fully understand the reason for the renaming

Make naming more clear to distinguish between server and mcp server

Which Server is being referred to here?
Isn’t the package-level distinction enough?

Also, by reserving the names McpClient and McpServer, we lose the ability to follow the same pattern as in the typescript and python sdks, where we have both Server / Client and the higher-level McpServer / McpClient

[kpavlov]

See #364