AmbitGet startedFAQReferenceGlossaryAll docsGitHubLive demo

Ambit and MCP gateways

An MCP gateway sits on the path of every tool call and decides whether it goes ahead. Ambit sits beside the agent, reads its configs into one local map, and says what the setup can do, whether it works, and what breaks if a piece goes. The two answer different questions and work together.

MCP gateways and governance proxies

A gateway sits between an agent and its MCP servers, on the path every tool call takes. Each call passes through it, and depending on the product it can allow the call, refuse it, hold it for a person, and log what happened. Lunar's MCPX is a gateway in that sense, with scoped permissions and an audit trail. AgentWard proxies each call and can allow it, block it or hold it for approval, and logs all three. Obsigno proxies calls to allow or deny them and records each decision in a signed ledger; it calls itself an evidence layer, not a general gateway. Diagrid's Catalyst puts a policy proxy in front of each MCP server.

A gateway answers may this call go ahead, now? It sees calls as they happen, so it knows what was attempted.

A third kind, discovery tools, answers which servers exist at all: Akto finds MCP servers across an organization's networks, cloud and registries.

Ambit

Ambit works beside the agent and does not need to be on the call path. It reads the configs of Claude Code, Cursor, OpenCode, Windsurf, Gemini CLI, Claude Desktop, Codex CLI and others into one local graph, and answers questions about the setup as a whole:

Ambit has a gate too, and it is the guardrail, not the center. ambit can returns ALLOW, CONFIRM or DENY for an action, approvals are signed artifacts the executor verifies, and a grant narrows itself on one failing check. Two parts sit on the call path when you route calls through them: the control plane, and in Claude Code the ambit gate hook, which answers every tool call and can only deny or ask, never allow. The center is the map and the session history.

Side by side

A gateway Ambit
Where it runs On the path of every tool call Beside the agent; reads configs and records work
What it sees Calls as they are made The whole setup, including what was never called
Main question May this call go ahead? What can this setup do, does it work, and what breaks if a piece goes?
Approvals Per call, as it happens Per change to the setup, as a signed, reviewable proposal
Where data lives Varies: some run on your machine, others as a hosted or self-hosted service One local SQLite file; nothing leaves except through a command you typed

Using both

They compose. A gateway decides call by call; Ambit says which calls are worth allowing without asking, from evidence that a capability has passed its check and been used without trouble. A person sets the threshold once, and the grant widens when the evidence reaches it and narrows again on one failing check.

To try Ambit, open the hosted demo, or run npx ambit-cli on your machine (brew install zz-plant/tap/ambit keeps the command). Where each AI agent keeps its MCP config lists what it reads.

See what your own agents can reach

Ambit reads the MCP configs of Claude Code, Cursor, OpenCode and thirteen more agents into one local map: every server, which ones work, what one more step would open, and what breaks if a piece goes.

Open the live demoa sample setup in your browser, nothing to install

On your machine: npx ambit-cli, with Node 22.18 or newer on macOS or Linux.

MIT licensed · one local SQLite file, no telemetry · on npm and in the official MCP registry