In-depth architectural comparison of the Openapi Mcp Gateway and Mcp Gateway 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
Openapi Mcp Gateway
Aggregators · Local stdio
Quality: 49/100 (Fair) | Auth: other
Mcp Gateway
Aggregators · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Openapi Mcp Gateway if you need specialized Aggregators tools running via a local process. Choose Mcp Gateway 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 Openapi Mcp Gateway when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: Mounts multiple OpenAPI specs with separate paths and authentication, Exposes FastAPI applications over ASGI, Provides dynamic list, get, and call meta-tools.
Mount many OpenAPI specs (or your existing FastAPI app) as MCP servers in one process. Auto-promotes eligible GETs to MCP resources, exposes huge specs via three list/get/call meta-tools instead of N tool schemas, and ships per-user OAuth2 token relay with audience-bound tokens.
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.
Category & Scope
Tools & Capabilities Breakdown
Openapi Mcp Gateway Tools (6)
Mounts multiple OpenAPI specs with separate paths and authentication
Exposes FastAPI applications over ASGI
Provides dynamic list, get, and call meta-tools
Auto-promotes eligible GET operations to MCP resources
Supports JSONata request and response shaping
Supports bearer, API-key, and OAuth2 authorization
Mcp Gateway Tools (26)
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).
Openapi Mcp Gateway is categorized under Aggregators and uses a local stdio subprocess. In contrast, Mcp Gateway belongs to Aggregators using local stdio subprocess. Select Openapi Mcp Gateway when you need capabilities focused on aggregators and Mcp Gateway when you require tools for aggregators.
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
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.