What runtime does mcp-http-proxy require?
The proxy runs on Node.js. No other runtime dependencies are mentioned; the MCP server it manages is expected to be a separate process.
@spontaneous-order
基本情報
An HTTP/SSE proxy server for Model Context Protocol (MCP) applications using stdio. Supports raw JSON-RPC commands via HTTP and implements direct stdio communication without an MCP SDK.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"mcp-http-proxy": {
"command": "node",
"args": [
"rpc-proxy-worker.js"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
mcp-http-proxy is an HTTP/SSE intermediary proxy server that manages a stdio-based MCP (Model Context Protocol) server process and exposes its tools and resources over standard HTTP and Server-Sent Events. It is designed for developers and applications that need to interact with MCP processes without handling stdio directly.
Run the script rpc-proxy-worker.js with Node.js (no additional install steps besides having Node.js). The server starts on port 3005 by default, serving a web dashboard at http://localhost:3005. Clients interact via HTTP endpoints (e.g., GET /tool/:toolName, POST /rpc/raw/command) or by connecting to the SSE endpoint at /sse.
tools/call requests.The proxy runs on Node.js. No other runtime dependencies are mentioned; the MCP server it manages is expected to be a separate process.
Clients send HTTP requests to endpoints like `/rpc/raw/command` (raw JSON-RPC) or `/tool/:toolName` (URL parameter style). The proxy forwards these as JSON-RPC commands to the child MCP process via stdin, and returns the response from stdout. Asynchronous events are pushed over SSE.
The main endpoints are: `GET /` (dashboard), `GET /tools`, `GET /tool/:toolName`, `POST /rpc/raw/command`, `GET /sse`, `GET /help`, and several debugging endpoints (`/rpc/command`, `/rpc/raw`, `/debug`).
It returns HTTP status codes (e.g., 404 for unknown tools, 400 for invalid parameters) and validates parameters for `/tool/:toolName`. Errors from the MCP process are relayed back in HTTP responses or pushed via SSE.
The README does not mention any authentication mechanism. The proxy is designed for local or trusted network use.
Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Remote MCP server for domain and website checks: DNS, WHOIS/RDAP, domain age, TLS, DNSSEC, email auth (SPF/DKIM/DMARC), blocklists, a trust verdict ("should my agent click, sign in to, or pay this site?"), availability +
コメント