AmbitGet startedFAQReferenceGlossaryAll docsGitHubLive demo

Ambit documentation

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. Run it once to see what you have, and again after any change: a piece whose check has stopped passing shows up as failing.

The claim underneath is that what an agent setup can do is not written in any config file: it is composed, a configured piece may not work, and none of it says what the setup is allowed to do. From A to B: the seven steps walks one setup through using it, and The ideas behind Ambit is the argument on one page.

What it reads and answers today

Why it exists

Where it is going

What changed, and what was said at the time

Both record what was said when it was written, so neither is revised afterwards.

Changing it

Workflow and the checks CI runs: CONTRIBUTING. The invariants a change must not break: AGENTS. Reporting a vulnerability: SECURITY. Every other question: SUPPORT. How to behave while doing it: Code of Conduct.

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