#73 · Primary category: AI Gateway & API Infrastructure

mcp-remote

mcp

Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server.

Project last updated:08/28/26

GitHub Stars

1.6K

Forks

285

Contributors

55

License

MIT

Why we included this project

Most MCP clients, including Claude Desktop, Cursor, and Windsurf, still expect to launch their servers as local subprocesses over stdio, which rules out pointing them at a server hosted on the web. mcp-remote is a small command-line bridge that speaks stdio to the client on one side and HTTP+SSE to the remote server on the other, and it handles the OAuth authorization flows that hosted access now requires. You add it as a normal entry in the mcpServers config block, point npx mcp-remote at the remote endpoint, and the client never notices the difference. A --header flag lets you send extra headers, such as a bearer token the remote server expects. The project is an honest proof of concept and the maintainers call it experimental, so treat it as a stopgap for reaching hosted servers today rather than a permanent fix for clients that have not shipped native remote support yet.

Articles for this project

No articles for this project yet.

To suggest a topic or contribute an article, contact us.

Related projects in this category