View on GitHubConnect an MCP Client that only supports local (stdio) servers to a Remote MCP Server.
About Mcp Remote
mcp-remote connects an MCP client that only supports local stdio servers to a remote MCP server. The README says it supports OAuth authorisation, custom headers, several transport strategies, tool filtering, proxy settings and debug logging. It has no tools of its own and simply relays the remote server.
It needs Node.js 18 or later and a client that runs local stdio servers, such as Claude Desktop, Cursor or Windsurf, plus the URL of the remote server. There is no separate install step. You add an entry to the client's JSON configuration that runs it through npx with the server URL. The repository is under the punkpeye account, and the README credits Glen Maddern as the original author. It is licensed MIT, and the README does not call it official. Details come from the project's README.
Key features
- Stdio to remote server bridge
- OAuth support
- Custom headers
- Tool filtering
- Runs through npx
More other MCP servers
- Other

Mcp Proxy
sparfenyuk
A bridge between Streamable HTTP and stdio MCP transports
2.8K GitHub starsPythonMIT - Other

Kanzo
emanuele-em
Self-hosted, sharable kanban for humans and agents. One 4.5 MB binary, 4.5 MB of RAM, 10 to 60 tokens per agent reply, starts in 2 ms, zero setup.
1.2K GitHub starsRustAGPL-3.0 - Other

čå PPT.skill
zhouwei713
įæåįūååŊįžčūåį PPT į Agent Skill
484 GitHub starsPythonMIT - Other

mcptoon
activeing123
MCP tool discovery burns 71,929 tokens. mcptoon drops it to 581 (â99.2%, measured). Zero dependencies.
431 GitHub starsPythonApache-2.0 - Other

automcp
NapthaAI
Easily convert tool, agents and orchestrators from existing agent frameworks to MCP servers
303 GitHub starsPythonApache-2.0