> The fact that you need to write a client for your client is...
correct me if im wrong, but isnt that a proxy? why is everyone calling it a server
correct me if im wrong, but isnt that a proxy? why is everyone calling it a server
Could also be called a gateway, which feels a bit more accurate.
The same way API gateways perform additional services like rate-limiting and authentication and billing, an MCP gateway abstracts the services behind it and adds context such that an LLM can more easily interact with them.
If you squint hard enough you can call almost any server a proxy. An FTP server is a proxy for data on disk. Github.com is a proxy for a git repo.
But yeah, saying "MCP is a proxy to your application" might be more insightful than "MCP is a client to your application"