mcp-proxy-server

> why we not just use API Did you meant to write "a HTTP API"? I asked myself this question before playing with it a bit. And now I have a slightly better understanding, I think the main reason was created as a way to give access of your local resources (files, envvars, network access...) to your LLM. So it was designed to be something you run locally and the LLM has access. But there is nothing preventing you making an HTTP call from a MCP server. In fact, we already have some proxy servers for this exact use-case[0][1]. [0] - https://github.com/sparfenyuk/mcp-proxy [1] - https://github.com/adamwattis/mcp-proxy-server