mcp-gateway

A gateway that translates MCP traffic between Claude Desktop’s stdio-based MCP client and HTTP/SSE-based MCP servers by accepting stdio requests, forwarding them to an SSE MCP server, and converting the responses back to the stdio MCP format.

Evaluated Mar 30, 2026 (22d ago)

Homepage ↗ Repo ↗ DevTools mcp model-context-protocol claude gateway sse stdio

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses an HTTPS default upstream URL (suggesting transport security is available), but the README does not describe authentication/authorization, scope control, or how sensitive data is logged/handled. No explicit secret-handling guidance is provided. Dependency inventory is minimal from manifest (not enough to assess CVE status from provided data).

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You control your local Claude Desktop setup and need a lightweight protocol translator to reach an MCP SSE endpoint.

Avoid When

You need well-documented security controls, rate-limiting behavior, or strong reliability semantics (retry/idempotency guidance) from the gateway itself.

Use Cases

• Connect Claude Desktop to existing HTTP/SSE MCP servers without rewriting the servers
• Bridge protocol compatibility when an MCP ecosystem uses mixed transport types (stdio vs HTTP/SSE)
• Quickly test or integrate MCP services behind an SSE transport into Claude Desktop

Not For

• A general-purpose public API gateway for arbitrary HTTP services
• Use cases requiring strong built-in authentication/authorization between gateway and upstream MCP server (not described)
• Production environments needing documented operational guarantees (SLA/retries/idempotency) from this project

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: Environment variable configuration for upstream MCP server URL (no auth method described for the gateway itself)

OAuth: No Scopes: No

The README describes selecting the upstream MCP server URL but does not document any authentication mechanism (API keys, OAuth, bearer tokens) between the gateway and the upstream SSE MCP server.

Pricing

Free tier: No

Requires CC: No

No pricing information is provided for the gateway itself; however the upstream MCP server (default MCP Hub) could have its own usage costs/limits not described here.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Gateway behavior depends on MCP_SERVER_URL/upstream server capabilities; mismatches between expected tool schema/transport behavior may surface as runtime failures.
⚠ The gateway is installed globally and then invoked via a local node command path in Claude Desktop config, which can be brittle across environments/paths.

Alternatives

Run or deploy a stdio-based MCP server variant for the same underlying capability Use an MCP SSE-to-stdio adapter/middleware that explicitly documents auth, retries, and error handling If available, use an MCP server that supports both stdio and HTTP/SSE transports

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-gateway.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.