mcp-remote
mcp-remote lets an MCP client that only supports local stdio servers talk to a remote MCP server, including servers that require OAuth. The README's reasoning is that most MCP servers are still installed locally, but the newer MCP authorization specification makes it possible to host servers remotely and share them without everyone running code on their own machine. It describes itself as a working proof of concept and says to treat it as experimental.
Configuration is a standard `mcpServers` entry that runs `npx mcp-remote <server URL>`, used the same way in Claude Desktop, Cursor and Windsurf. Options covered include `--header` for custom or bearer-token headers (with a workaround for clients that mangle spaces in `args`), `--resource` to run several instances of the same server with separate OAuth sessions (for example different Atlassian tenants), adding `-y` or `@latest` to `npx`, a configurable OAuth redirect port, static OAuth client metadata and client information, and transport strategies. It is MIT licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-20
- Commits, last 90 days
- 98
- Releases, last 90 days
- 30
- Latest release
- v0.15.2 (2026-10-20)
- Open issues
- 2
- Recent issues with at least one comment
- 14/21
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #384 [FEATURE REQUEST] Make the listen interface configurable0 comments · 2026-10-23
- #382 CIMD (DCR) support0 comments · 2026-10-19
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!