Ambit

Name: Ambit
Author: zz-plant

by zz-plantversion 0.6.0i★ –iRuns on your computer

Registry nameio.github.zz-plant/ambit

Install

Overview

Description from the maker (original English)

Capability graph of your agent stack: what it can do, what to set up next, what breaks.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ambit": {
      "command": "npx",
      "args": [
        "-y",
        "ambit-cli",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add ambit -- npx -y ambit-cli mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ambit": {
      "command": "npx",
      "args": [
        "-y",
        "ambit-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ambit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ambit-cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account zz-plant, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32706 servers in this category
Published to the registry more recently than 56% of the other 32706 servers in this category
Basic checks equal to or better than 100% of the other 32706 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ambit safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.6.0) reached the registry 32 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Kanal Varna — drains, leaks & plumbing (Varna, BG)

by kanalvarna.com

Drain unblocking, leak detection & plumbing in Varna, Bulgaria: services, prices, areas, contact

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Ambit

A Civilization-style tech tree of what your AI agents can do, and what one more step would unlock.

Ambit reads the configs of Claude Code, Cursor, OpenCode and 13 other agent runtimes into one local map. What you, your agents and your machines can jointly do is your *ambit*: this shows where its edge is and how to move it.

Try the live demo · Get started · Connect it to your agent · FAQ · Docs

Pick a next step and the map shows what it opens. Switch off something you rely on and it counts what stops.

npx ambit-cli, or brew install zz-plant/tap/ambit && ambit, or open the hosted demo and install nothing.

What it tells you

What is one step away. Capabilities whose prerequisites you already meet, each with a setup estimate, ranked by what keeps blocking your agents and by how much each step opens. Tools also compose: a vector store plus local embeddings gives you semantic retrieval, which neither config mentions.
What is configured but not working. ambit verify runs a capability's declared check. One that fails is left out of plans and permissions until it passes.
What your tool lists cost. ambit weigh starts each local tool server your user-level configs declare and measures what its tool list takes from context every session.
What stops if a piece goes. Three providers that share one API credential show up as one point of failure.

Your agents can ask the same questions over MCP: what they can do before they try, and at a limit, what would lift it, drafted as a change you approve. Ambit is a *meta-MCP server*, speaking the protocol of the tools it reads. The graph is a local SQLite file, with no telemetry.

On a small setup, Ambit mostly answers what to add next. On a larger one, with several runtimes and a second machine, it mostly answers which configured tools fail their checks and what would stop with them. The words it uses are defined further down.

If it answers a question your config files could not, a star is how the next person with the same stack finds it.

Get started

Way in	What it gives you
In the browser	Open the hosted demo for a sample setup, or drop in your own MCP config from Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, Cline, Roo Code, Copilot CLI, Kiro or OpenCode, and it is placed on the map in the tab, uploading nothing, with what one more step would open for it. No file at hand? Tick the servers you run.
On your machine	`npx ambit-cli` (Node 22.18 or newer), or `brew install zz-plant/tap/ambit && ambit`, reads your real agent configs, names what it found, and shows what one more step would open. It ends on one thing to do, `npx ambit-cli web`: the same readout on the map, served on localhost. `npm install -g ambit-cli` puts `ambit` on your path.
With the map	`git clone https://github.com/zz-plant/ambit.git && cd ambit && ./bootstrap.sh web` builds the graph from your own configs and serves the map the pictures on this page show.
In a cloud IDE	A full checkout with the map running, in a browser tab, touching nothing on your machine. The container holds none of your configs, so the map it shows has nothing of yours on it: a way to try the code, not to map your setup.
From your agent	Register Ambit over MCP and the agent can ask what it is able to do before it tries. Connect it to your agent has the snippet.

npm installs the tagged release on macOS, Linux and Windows, and Homebrew on macOS and Linux. On Windows ./bootstrap.sh does not run, ambit weigh cannot start a server launched through a .cmd such as npx, and a check written for sh stays unverified unless Git Bash or another sh is on the PATH. ./bootstrap.sh discovers OpenCode, Claude Code, Cursor, Windsurf, Gemini CLI, Claude Desktop, Codex CLI, Cline, Roo Code, Continue, Zed, VS Code, Copilot CLI, Amp, Goose and Kiro, the skill directories ~/.agents/skills, ~/.opencode/skills and ~/.config/opencode/skills, and the models Ollama and LM Studio keep on disk, builds a local SQLite graph, prints the same readout npx ambit-cli does, and links ambit into ~/.local/bin when that directory is on your PATH (or prints the ln -s line when it is not). ./bootstrap.sh --dry-run writes nothing: it reports whether there is an OpenCode config, a running Ollama and a skills directory.

My Setup lists every server, agent, and model found on the machine: whether it is on, what its check said, and which capabilities on the map it provides

Where Ambit sits in the stack

Ambit sits above the protocol layer and below workflow orchestration. Its CLI, MCP server and gate neither route an agent's calls nor run them. The one part that can run an agent's step is the control plane, which you start yourself from a checkout, and only with its opt-in Docker adapter.

If you want to	Use	What Ambit adds
Find a tool by name or description	Smithery, the MCP registries, tool-RAG	Which ones your setup already has what it needs for, and what each would open
Order the steps of one task	A workflow engine such as LangGraph	Nothing inside the task; what the setup can do before one starts
Install a binary	Nix, Homebrew	No installing; what is missing, in order, as a change you approve
Allow or refuse each call as it happens	An MCP gateway	No place on the call path; Ambit's gate only answers Claude Code's hook, with deny or ask
See what the whole setup can do, which pieces work, and what to add next	Ambit

For the architectural foundation, economic loop, and comparison to prior work, see The ideas behind Ambit, Your loadout, from A to B, and Building alone.

Ask from the terminal

Command	What it answers
`ambit status`	Environment health: what is reached and how much of it is verified, what is failing its declared check, what has a single provider, pending approvals, and the one command to type next
`ambit goal`	The path to unlock a capability, in order, with setup estimates
`ambit repo [dir]`	What to add for the project you are in, from its dependencies and the servers you already run
`ambit impact`	What downstream stops working if this dependency fails
`ambit graph combos`	Compound capabilities, including the ones you are one prerequisite away from
`ambit authority`	Per-action permissions: what runs unattended, what needs confirmation
`ambit verify [id]`	Run a capability's declared check and record whether it passes
`ambit weigh`	What each tool server's tool list costs in context every session, per runtime, and which ones the ledger never saw called
`ambit history [since [ ]]`	How the frontier moved, separating what you acquired from what emerged
`ambit share`	A self-contained HTML snapshot of the map, written locally and safe to post

ambit help covers a first session. ambit help plan, or any of the five group names, lists what that group holds, one line a command; ambit help goal shows one command with its options, ambit help frontier explains one word, and ambit help --all is the full surface. --help after any command says what it does without running it.

The commands above read the capability graph. A second group (attention, work, usage, opportunities, roi, audit) reads a local work ledger: the human time and cost of running the stack. Until sessions are recorded they say which data is missing instead of printing a number, and they say more once a few weeks are recorded. The FAQ explains how to start recording.

ambit status — where the environment stands

$ ambit status

15 of 46 reached, and 20 of your own · 0 verified · 8 with a single provider ──────────────────────────────────────────────────────────────────────── verified 0 › unverified 15 11 provable now · 4 with no check failing 0 entries 24 from your config, and 4 built into the runtime last check never

Provable now Automated Tests, Browser Automation, Code Intelligence, Continuous Delivery, Data Access, File Editing, Local Runtime, Shell Execution and 3 more

By domain ████░░░░░░ ai-ml 5/13 ██████░░░░ backend 7/11 █████░░░░░ devops 4/8 …

Next ambit verify · turns 11 of the unverified into evidence

<!-- /example -->

This is a fresh graph, before any check has run: reached and verified lead, the curated capabilities first and then the servers, models and runtimes of your own, the four counts under the rule add up to the two reached figures together with the four built-ins every runtime brings, the › marks the count that wants a person, and the last line names the next command to type. CI captures the block from a fixture graph and fails if it drifts from what the command prints.

ambit impact — downstream dependency impact

$ ambit impact mcp:playwright

If playwright went away ─────────────────────── › Stops working Automated Tests, Browser Automation, Continuous Delivery, Observability · and the 3 actions they confer Survives Tool Protocol (12 other providers)

<!-- /example -->

Affected capabilities are listed first, marked with ›, through the full dependency chain: if Continuous Delivery requires Automated Tests, it fails as well. Surviving capabilities show their remaining provider count, accounting for shared credentials that would fail together. Given a credential, impact answers what revoking it ends, matching ambit credentials.

ambit share — what may leave the graph, and what may not

ambit share builds its HTML from an allow-list: name

Only the beginning is shown; read the rest in the repo

Ambit

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Kanal Varna — drains, leaks & plumbing (Varna, BG)

README from the maker

Ambit

What it tells you

Get started

Where Ambit sits in the stack

Ask from the terminal

ambit status — where the environment stands

ambit impact — downstream dependency impact

ambit share — what may leave the graph, and what may not