What Portkey MCP Gateway does
The MCP Gateway is Portkey’s solution for managing access to MCP servers. It acts as a proxy between MCP Clients and MCP servers, handling authentication, access control, and logging.
Why teams reach for it: Centralizes workspace-level rate limits for MCP tool calls without changing existing LLM rate-limit policies.
Worth knowing
MCP Gateway handles authentication, access control, and logging for MCP servers; requires API keys or OAuth for authorization; supports multiple providers and models; includes observability features.
How Portkey MCP Gateway compares
Fields the vendor doesn't document are left blank here rather than guessed — a blank means nothing verified, not a "no."
- Transports Client Facing
- Streamable HTTP
- Transports Server Facing
- Streamable HTTP
- Server Aggregation
- No
- Hosts Stdio Servers Remotely
- No
- Terminates Auth
- Yes
- Rbac
- Yes
- Tool Filtering
- Yes
- Agent Identity
- Yes
- Policy Enforcement
- Built-in engine
- Audit Logging
- Yes
- Telemetry Output
- OpenTelemetry
- Also Proxies
- LLM inference, A2A, REST, gRPC
- Deploy Targets
- Kubernetes
- Self Hostable
- Yes
How will you route, mediate, and control traffic?
A gateway or proxy sits between clients and MCP servers to route traffic or add a control layer, without changing the servers themselves.