<div align="center"
Ambit
What you, your agents, and your machines can jointly do — and where your own time is going.
Ambit reads the configs of Claude Code, Cursor, OpenCode, Windsurf, Gemini CLI, Claude Desktop and Codex CLI into one local graph, and answers what no single config file can: what works, what is configured but broken, and what stops working if one MCP server, model or token goes away.
Try the live demo · Get started · Connect it to your agent · FAQ · Docs
<br
<img src="docs/assets/capability-graph-demo.gif" alt="Ambit showing one developer setup as a map: Shell Execution is selected and its dependents listed, switching it off turns what depends on it red and says nine working capabilities would stop, apart from those never set up and one already failing, a second view colors the tools that interrupt a person most often, and a proposed config change waits for approval" width="920"
<subOne setup, mapped. Pick a capability and Ambit shows what depends on it; switch it off and it counts the nine working things that would stop, apart from the ones never set up and the one already failing. Then which tools interrupt you most, and a change waiting on your approval.</sub
brew install zz-plant/tap/ambit && ambit, or open the hosted demo and install nothing.
</div
---
What Ambit is
Ambit (from Latin ambitus: circuit, perimeter, sphere of action) is the boundary of what you, your agents, and your machines can jointly and reliably do.
If you use AI agents, your setup is spread across LLM providers, MCP servers, local CLI tools, skill directories, credentials, and more than one machine. Every piece has its own config file.
What they add up to — what your human-plus-agent system can actually do — is written down nowhere.
Ambit reads those configs and builds one map out of them. Every tool, model, skill, and credential becomes a point on it; everything one of them needs in order to work becomes a line to another. That map answers questions no single config file can:
- What works right now? Distinguishing what is merely configured from what is proven to work (installed ≠ working ≠ authorized).
- What breaks downstream if a model, tool, or credential goes away (transitive blast radius and shared single points of failure).
- What compound abilities emerge when two independent tools are combined.
- What is worth setting up next, priced by the human attention it would save.
You ask from the terminal. Your agents ask over MCP, mid-session, before they run into the limit — Ambit is itself an MCP server, so the thing describing your MCP servers speaks the same protocol they do. (A meta-MCP server, if you want the term to search for.)