{
  "markdown": "# @nimbus-dev/mcp\n\n## What this is\n\nA tiny launcher that exposes your local [Nimbus](https://nimbus-agent.dev) index and agents to\nany [MCP (Model Context Protocol)](https://modelcontextprotocol.io) client — editors, chat clients,\nor other MCP-speaking tools. It does no work itself: it locates the Nimbus CLI binary already\ninstalled on your machine and execs it as `nimbus mcp-server --stdio`, then gets out of the way and\nlets stdio pass straight through.\n\nThis package is MIT-licensed and does not depend on (or import from) the AGPL-3.0 `packages/cli` or\n`packages/gateway` Nimbus source — it only knows how to *find* the installed binary, never how to\nrun the gateway itself.\n\n**Requires the Nimbus gateway to already be installed.** This launcher does not install or bundle\nNimbus; run the regular [Nimbus installer](https://nimbus-agent.dev/user-guide/install/) first, and\nkeep the gateway configured the way you normally use it (the `mcp-server --stdio` command talks to\nyour existing local index).\n\n## Scope\n\nFinding the binary, spawning it with stdio inherited, and staying in the process tree only long\nenough to translate the child's exit status back to the client is the whole job. Keeping it that\nway is what lets this package stay MIT while the gateway it launches is AGPL-3.0. Specifically,\nit does not:\n\n- **Install, bundle, update, or version-check Nimbus.** Use the regular Nimbus installer.\n- **Implement any MCP tools.** The index and agent tools are served by `nimbus mcp-server` in the\n  [Nimbus](https://github.com/nimbus-agent/Nimbus) monorepo (`packages/cli`, `packages/gateway`).\n  A tool that is missing or misbehaving is a bug there, not here.\n- **Parse, filter, proxy, or rewrite the MCP stream.** The child process inherits stdio, and traffic\n  passes through untouched in both directions.\n- **Manage gateway configuration, authentication, or the index itself.** Configure those the way you\n  normally do; this launcher passes your environment through unchanged and otherwise stays out of\n  the way.\n- **Take on runtime dependencies.** `package.json` has `devDependencies` only. That is a licence and\n  supply-chain boundary rather than a style preference — adding a runtime dependency here is a\n  deliberate decision, not a convenience call.\n\n## Install\n\nRun it directly, without a global install, from your MCP client's config (see below), or install it\nexplicitly:\n\n```bash\nnpm install -g @nimbus-dev/mcp\n```\n\n## Quickstart\n\nAdd `nimbus-mcp` as a command in your MCP client's server configuration, for example:\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@nimbus-dev/mcp\"]\n    }\n  }\n}\n```\n\nClients that install from the [MCP Registry](https://registry.modelcontextprotocol.io) can find this\nserver listed as `io.github.nimbus-agent/nimbus`.\n\n### Running from a local checkout\n\nTo run the launcher straight from a clone of\n[this repository](https://github.com/nimbus-agent/nimbus-mcp) — when developing it, or to try a\nchange before it is released — point your MCP client at the entry point itself. Use absolute paths:\nan editor-spawned MCP server does not inherit your shell's working directory.\n\n```json\n{\n  \"mcpServers\": {\n    \"nimbus\": {\n      \"command\": \"bun\",\n      \"args\": [\"/absolute/path/to/nimbus-mcp/src/index.ts\"]\n    }\n  }\n}\n```\n\nIf you already have the Nimbus CLI installed, you can skip the launcher altogether and have your\nclient run `nimbus mcp-server --stdio` directly — the launcher exists only to find that binary for\nyou.\n\n### How the binary is found\n\nThe launcher looks for the Nimbus binary in this order:\n\n1. `NIMBUS_BIN` — an explicit full path to the binary, if set. A `NIMBUS_BIN` that points at a\n   non-existent file is reported as an error, never silently ignored.\n2. `PATH` — the first `nimbus` (or `nimbus.exe` on Windows) found on your `PATH`.\n3. Known per-platform install directories, the installer's own output directory first, then the\n   directories the other Nimbus distribution channels write to:\n\n   | Platform | Searched in order |\n   |---|---|\n   | Windows | `%LOCALAPPDATA%\\Programs\\Nimbus\\bin` (installer and `.msi`/winget), then Scoop's shims — `%SCOOP%\\shims` or `%USERPROFILE%\\scoop\\shims`, then `%SCOOP_GLOBAL%\\shims` or `%ProgramData%\\scoop\\shims` |\n   | macOS | `~/.local/bin` (installer and `.pkg`), then `/opt/homebrew/bin` and `/usr/local/bin` (Homebrew) |\n   | Linux | `~/.local/bin` (installer), then `/usr/local/bin` (apt/yum) and `/usr/bin`, then `/home/linuxbrew/.linuxbrew/bin` and `~/.linuxbrew/bin` (Homebrew) |\n\nStep 3 is what carries a GUI-launched editor on macOS, which typically spawns MCP servers without\nyour shell's `PATH`. If none of those resolve, the launcher exits with a message naming the fix —\nnever a bare exit code.\n\nIf you installed Nimbus somewhere else entirely, set `NIMBUS_BIN` rather than waiting for a\ndirectory to be added here.\n\n### Environment variables\n\n- `NIMBUS_BIN` — override the resolved binary path. Point it at the exact Nimbus CLI executable.\n- `NIMBUS_MCP_TIMEOUT_MS` — how long the Nimbus **CLI's MCP adapter** waits for an agent brief\n  before returning a clean timeout error; it defaults to 60 s. Lower it when your editor's own MCP\n  transport timeout is shorter, so the tool reports a timeout instead of having the call severed\n  underneath it. This is the adapter's own budget — the gateway imposes no such timeout. It is read\n  by the underlying `nimbus mcp-server` process, which this launcher execs with your environment\n  inherited unchanged.\n\n## See also\n\n- [`docs/architecture.md`](https://github.com/nimbus-agent/Nimbus/blob/main/docs/architecture.md) —\n  Nimbus subsystem design and the MCP connector standard.\n- The gateway's `mcp-server` command, in the main [Nimbus](https://github.com/nimbus-agent/Nimbus)\n  repository (`packages/gateway`, `packages/cli`) — this package launches it, but does not contain\n  or license it.\n\n## License\n\nMIT — see [`LICENSE`](./LICENSE). Note that the Nimbus gateway and CLI this launcher execs are\nlicensed separately under AGPL-3.0.\n",
  "bytes": 6065,
  "sha": "477f99022a6cd6db41d75f3dfe9d9b9e2d64f138a44a1983fac7a0181d3aff3b",
  "repo_slug": "nimbus-agent/nimbus-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_nimbus_agent_nimbus_f2dd7697/readme"
}