Guide
Should your API gateway serve MCP tools?
An API gateway can be a practical place to expose REST operations as MCP tools when it can translate calls, reuse the API’s authentication and quotas, and let you select exactly which operations agents may invoke. It does not automatically make every API safe for agent use: tool descriptions, authorization scope, side effects, and human approval still need deliberate design.
“MCP gateway” can mean two different paths. An inbound MCP server exposes your existing business APIs to agents as tools. An outbound LLM gateway routes your application’s model requests to providers. Some products cover one path; a platform may cover both, but that does not imply the two features share policies or can be enabled together.
Why this is timely
Cloud gateways have started adding native MCP exposure. Google Cloud API Gateway documents a Public Preview that derives tool operations from OpenAPI 3.x; Google also announced MCP support in Apigee hybrid, where the MCP data plane runs in the customer’s cluster. Preview scope changes, so verify the current documentation before committing an architecture.
Choose the deployment pattern
| Pattern | Good fit | Main trade-off |
|---|---|---|
| Existing API gateway translates REST to MCP | APIs already have accurate OpenAPI contracts and established auth, quotas, and logs. | Protocol support may be limited; gateway policy must understand tool discovery and invocation. |
| Dedicated MCP server | Tools need custom orchestration, resources, prompts, long-running work, or a protocol feature the gateway lacks. | You own another service, identity boundary, deployment path, and monitoring surface. |
| Both | Use an API gateway for stable REST-backed tools and dedicated servers for specialized capabilities. | Inventory and govern two tool surfaces; prevent overlapping names or inconsistent authorization. |
Check the limits before adopting a preview
Google’s API Gateway overview currently lists `initialize`, `tools/list`, and `tools/call` over HTTP, with OpenAPI 3.x configuration. It says resources and prompts, stdio transport, streaming or long-running tool calls are not supported, and MCP and model routing cannot be enabled in the same API configuration. Those are product-specific limits, not MCP-wide limits.
A safe rollout
- Start with a read-only API operation and a narrow OpenAPI schema.
- Expose only approved operations; deny destructive methods by default.
- Require authentication for discovery if tool names or schemas are sensitive, and enforce the same or stronger authorization on invocation.
- Log the principal, tool name, decision, result status, and correlation ID without copying sensitive payloads unnecessarily.
- Test malformed arguments, expired credentials, rate limits, timeouts, retries, and attempted cross-tenant access.
- Keep a direct API path or rollback switch while preview behavior is being evaluated.
Use the gateway when it centralizes controls already applied to the REST API and meets the protocol needs of the workload. Choose a separate MCP server when you need richer MCP features, custom tool semantics, or an independently controlled release cycle.
For the outbound model path, see what an LLM gateway does. For the control questions that remain after choosing a pattern, read the gateway compliance evidence guide.
Common questions
Is an API gateway the same thing as an MCP server?
No. An API gateway can implement an MCP server role by translating MCP tool calls into REST operations, but an MCP server may also expose capabilities that the gateway does not support. Check the exact methods and transports implemented.
Does exposing an API as an MCP tool secure it automatically?
No. The gateway can reuse authentication and policy controls, but the team still needs to select tools, scope identities, protect discovery where appropriate, and test authorization at invocation.
Can one gateway route model calls and expose APIs as MCP tools?
Some products may support both features, but the configuration may not. Google Cloud API Gateway currently documents mutual exclusion between MCP exposure and its model-routing feature in one API configuration.
Sources and editorial review dates are recorded with this guide. Catalogue-backed blocks use the dated catalogue snapshot. See our methodology.