MAQPNA

Learn

What is an MCP gateway? And what it does for MCP security.

Agents reach tools through MCP servers. A gateway is the one place where every one of those calls can be checked.

Updated 1 November 2026.

FAQ

Common questions

Do I need an MCP gateway?

If agents call tools that can change data, spend money or send messages, yes. A gateway gives you one place to decide what is allowed, keep credentials away from the agent and record every call. For a single developer experimenting with read-only tools, it is less urgent.

Is an MCP gateway the same as an AI gateway?

Not quite. An AI gateway usually sits in front of model APIs and handles routing, keys and cost. An MCP gateway sits in front of tools. Some products do both. MAQPNA's gateway governs model calls and tool calls in the same pipeline.

Can an agent bypass the gateway?

It depends on the network. If the agent can reach MCP servers directly, it can bypass any gateway. MAQPNA runs each session in a sandbox with default-deny networking whose only exit is the gateway, and keeps upstream credentials out of the sandbox.

Does an MCP gateway stop prompt injection?

No gateway can stop a model being persuaded. What it can do is limit the damage: deny dangerous tools, require approval for risky arguments, block data leaving after the session has read untrusted content, and record what happened.

Put a gateway in front of every tool.

Run MAQPNA locally in one command and watch each MCP call your agent makes get a decision.

More install options
curl -fsSL https://maqpna.com/install.sh | sh