https://neon.com/blog/building-a-cli-client-for-model-context-protocol-servers https://neon.com/blog/building-a-cli-client-for-model-contex... might be of inter

https://neon.com/blog/building-a-cli-client-for-model-context-protocol-servers https://neon.com/blog/building-a-cli-client-for-model-contex... might be of interest. An MCP server provides enough metadata and self-documentation that it's quite straightforward to make a MCP-agnostic CLI client that adapts an arbitrary MCP server into a set of flags that allow you to call its explicit tools with explicit arguments - without ever needing to involve an LLM in the mix! You could even have that CLI tool launch the MCP server as a local subprocess, if you wanted - again, all deterministically. And if you want to have an SDK in any language under the sun, once you have an MCP outputting reasonable tool descriptions, any LLM could make a best-in-class SDK for you in a heartbeat following that language's best practices. So it's not unreasonable for someone working on a greenfield project to make an MCP server first nowadays!