mcp-remote MCP Server
punkpeye/mcp-remote
Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server.
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
punkpeye/mcp-remote is a TypeScript MCP server licensed under MIT. Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server. Topics: mcp.
Ranked #2 out of 24850 indexed tools.
In the top 1% of all indexed tools.
Has 1,603 GitHub stars.
Used by 216 other projects.
Has 60 contributors.
Actively maintained with commits in the last week.
Ecosystem
Score Breakdown
1,603 stars → well-known project
Last commit 4d ago → actively maintained
169/170 issues closed → responsive maintainer
60 contributors → active community
216 dependents → gaining traction
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
Matched Queries
From the README
# `mcp-remote` Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server, with auth support: ## Why is this necessary? So far, the majority of MCP servers in the wild are installed locally, using the stdio transport. This has some benefits: both the client and the server can implicitly trust each other as the user has granted them both permission to run. Adding secrets like API keys can be done using environment variables and never leave your machine. And building on `npx` and `uvx` has allowed users to avoid explicit install steps, too. But there's a reason most software that _could_ be moved to the web _did_ get moved to the web: it's so much easier to find and fix bugs & iterate on new features when you can push updates to all your users with a single deploy. With the latest MCP [Authorization specification](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization), we now have a secure way of sharing our MCP servers with the worlRead full README on GitHub →
Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.