mcp-proxy-server

mcp-proxy-server is an MCP proxy/hub that connects to multiple MCP resource servers (via stdio or SSE transport), aggregates their advertised resources/tools/prompts, and routes incoming MCP requests to the appropriate backend server(s) through a single unified interface.

Evaluated Mar 30, 2026 (0d ago)

Repo ↗ DevTools mcp proxy orchestration aggregation routing stdio sse typescript

⚙ 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

README shows passing environment variables (e.g., SECRET_API_KEY) to downstream server commands. No guidance is provided about redaction/logging, secret management, network exposure controls, or authentication for clients of the proxy. SSE transport is configured via http:// in example config, but TLS requirements are not stated.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You control the downstream MCP servers and want to compose/route among them for a local or controlled deployment (e.g., Claude Desktop, internal agent setups).

Avoid When

You need strong built-in auth/tenant isolation and documented operational safeguards for untrusted clients.

Use Cases

• Unifying multiple MCP tool/resource servers behind one MCP entry point
• Centralizing routing/aggregation logic for teams or agent deployments
• Composing a single agent capability set from multiple backend MCP services
• Simplifying Claude Desktop MCP server configuration by using a proxy instead of many backend servers

Not For

• Providing a public, internet-facing multi-tenant API without additional security controls
• Use cases requiring fine-grained authorization/scopes per downstream tool (not evidenced)
• Production environments needing documented SLAs, compatibility guarantees, or robust operational guidance (not evidenced)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication/authorization mechanism is described in the provided README. Downstream connectivity is configured via local commands/URLs and environment variables.

Pricing

Free tier: No

Requires CC: No

Open-source npm package; no pricing information provided.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Config-driven multi-server routing may introduce tool name collisions or ambiguity if downstream servers expose overlapping resources/tools (not documented).
⚠ Debugging can be challenging because downstream servers communicate over stdio (README notes this).
⚠ SSE behavior depends on KEEP_SERVER_OPEN; client disconnect handling is mentioned but not fully specified.

Alternatives

Run/aggregate at the agent layer (custom orchestrator that calls MCP servers directly) Use an MCP gateway/proxy solution with documented auth and operational controls If available, deploy a dedicated API gateway in front of your MCP servers (authn/authz + rate limiting) rather than only proxying

Full Evaluation Report

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

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.