local-mcp-gateway
Local MCP Gateway is a self-hosted control-plane/proxy that aggregates multiple MCP servers behind profile-specific HTTP endpoints, with a web UI for managing MCP servers, profiles, tools, logging/observability, and access control (API keys and OAuth 2.1).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README claims OAuth 2.1 support (PKCE, DCR) and API key management, plus organization/team RBAC. However, provided materials do not specify scope granularity, token lifetimes, rotation, CSRF protections, secure session storage, or whether the HTTP endpoints enforce HTTPS. Docker/local usage suggests transport is typically local, but TLS requirements for production are not described. Dependency hygiene and secret handling practices are not evidenced in the provided content.
⚡ Reliability
Best When
You want to self-host an MCP aggregation/gateway locally (often with Docker) and manage which tools are available to different clients/assistants.
Avoid When
You cannot support user authentication flows (signup/OAuth) or prefer a simple unauthenticated pass-through proxy.
Use Cases
- • Expose a curated subset of MCP tools to different AI assistants via profiles
- • Aggregate multiple MCP servers (stdio/SSE/remote) behind a single gateway endpoint
- • Team/shared management of MCP servers and profiles with role-based access control
- • Debug/inspect MCP request/response traffic through an observability UI
Not For
- • Publicly hosted, internet-facing services without additional hardening/ops controls
- • Environments requiring a strict, documented API contract for every gateway behavior without UI-based configuration
- • Use as a lightweight library/SDK for embedding into another backend
Interface
Authentication
Auth is described at a feature level (OAuth 2.1, API key management, team RBAC), but the README provided does not include concrete auth flows, endpoints, scope model, or exact token usage for the MCP endpoints.
Pricing
Self-hosted. README indicates Elastic License 2.0 and 'cannot be provided as a hosted service to third parties,' which affects commercial hosting/licensing decisions.
Agent Metadata
Known Gotchas
- ⚠ Requires authentication/signup and likely token/API-key setup before tool usage (details not provided in README).
- ⚠ Profile selection is dynamic via different MCP endpoint URLs; agents must use the correct profile path (e.g., /api/mcp/{profile}).
- ⚠ If used with Claude Desktop, HTTPS tunneling may be required to avoid SSL/certificate issues.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for local-mcp-gateway.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
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
Scores are editorial opinions as of 2026-03-30.