MCP Gateway vs MCP Access Point — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Gateway vs MCP Access Point
In-depth architectural comparison of the MCP Gateway and MCP Access Point MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Gateway
Aggregators · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
MCP Access Point
Aggregators · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Gateway if you need specialized Aggregators tools running via a local process. Choose MCP Access Point if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Gateway when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: PMCP_AUTH_TOKEN, PMCP_RATE_LIMIT.
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Protocol conversion between HTTP and MCP, Zero-intrusive integration with existing HTTP services, Supports SSE and Streamable HTTP transport protocols.
A meta-server for minimal Claude Code tool bloat with progressive disclosure and dynamic server provisioning. Exposes 9 stable meta-tools, auto-starts Playwright and Context7, and can dynamically provision 25+ MCP servers on-demand from a curated manifest.
Turn a web service into an MCP server in one click without making any code changes.
Category & Scope
Tools & Capabilities Breakdown
MCP Gateway Tools (26)
gateway.auth_connect
Store credentials for a server and make them available to provisioning. Use this when gateway.provision reports missing authentication.
gateway.cancel
Cancel a pending tool invocation. By default, refuses to cancel healthy requests (recent heartbeat). Use force=true to cancel anyway. Use gateway.list_pending first to see request IDs and health status.
gateway.catalog_search
Search for available tools across all connected MCP servers. Returns compact capability cards without full schemas. Use filters to narrow results by server, tags, or risk level. Set include_offline=True to also discover provisionable servers not yet running. This is the primary tool discovery entry point.
gateway.config_status
Show read-only effective configuration and startup policy status with source attribution and non-secret diagnostics.
gateway.connect_server
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Gateway is categorized under Aggregators and uses a local stdio subprocess. In contrast, MCP Access Point belongs to Aggregators using local stdio subprocess. Select MCP Gateway when you need capabilities focused on aggregators and MCP Access Point when you require tools for aggregators.
Connect or start a known downstream MCP server by name. Resolves configured, provisioned manifest, and registered discovered servers.
gateway.describe
Get detailed information about a specific tool, including its arguments and constraints. Use this before invoking a tool to understand its requirements.
gateway.disconnect_server
Disconnect a running downstream MCP server without changing persistent config. Refuses by default when that server has pending requests; set force=true to cancel them.
gateway.get_startup_policy
Return persisted autoStart and legacy disableAutoStart entries grouped by config source.
gateway.health
Get the health status of the gateway and all connected MCP servers. Shows server status, tool counts, and last refresh time.
gateway.invoke
Invoke a tool on a downstream MCP server. Arguments are validated against the tool schema before execution. Output is automatically truncated if too large.
gateway.list_pending
List all pending tool invocations with health status. Shows elapsed time, heartbeat age, and current state for each request. Use this to monitor long-running operations before deciding to cancel.
gateway.provision
Provision (install and start) a specific MCP server from the manifest. Use this after reviewing candidates from gateway.request_capability. Returns immediately with a job_id for tracking. Poll gateway.provision_status to check progress. Use gateway.request_capability instead if you don't know the exact server name.
+14 more tools listed on main page
MCP Access Point Tools (6)
Protocol conversion between HTTP and MCP
Zero-intrusive integration with existing HTTP services
Supports SSE and Streamable HTTP transport protocols
Multi-tenancy with per-service configuration and routing
Runtime configuration management via RESTful Admin API
Lightweight, high-performance proxy built on Pingora