Nimbus MCP server

@nimbus-dev/mcp

What this is

A tiny launcher that exposes your local Nimbus index and agents to any MCP (Model Context Protocol) client — editors, chat clients, or other MCP-speaking tools. It does no work itself: it locates the Nimbus CLI binary already installed on your machine and execs it as nimbus mcp-server --stdio, then gets out of the way and lets stdio pass straight through.

This package is MIT-licensed and does not depend on (or import from) the AGPL-3.0 packages/cli or packages/gateway Nimbus source — it only knows how to find the installed binary, never how to run the gateway itself.

Requires the Nimbus gateway to already be installed. This launcher does not install or bundle Nimbus; run the regular Nimbus installer first, and keep the gateway configured the way you normally use it (the mcp-server --stdio command talks to your existing local index).

Scope

Finding the binary, spawning it with stdio inherited, and staying in the process tree only long enough to translate the child's exit status back to the client is the whole job. Keeping it that way is what lets this package stay MIT while the gateway it launches is AGPL-3.0. Specifically, it does not:

Nimbus monorepo (packages/cli, packages/gateway). A tool that is missing or misbehaving is a bug there, not here.

• Install, bundle, update, or version-check Nimbus. Use the regular Nimbus installer.
• Implement any MCP tools. The index and agent tools are served by nimbus mcp-server in the

passes through untouched in both directions.

• Parse, filter, proxy, or rewrite the MCP stream. The child process inherits stdio, and traffic

normally do; this launcher passes your environment through unchanged and otherwise stays out of the way.

• Manage gateway configuration, authentication, or the index itself. Configure those the way you

supply-chain boundary rather than a style preference — adding a runtime dependency here is a deliberate decision, not a convenience call.

• Take on runtime dependencies. package.json has devDependencies only. That is a licence and

Install

Run it directly, without a global install, from your MCP client's config (see below), or install it explicitly:

npm install -g @nimbus-dev/mcp

Quickstart

Add nimbus-mcp as a command in your MCP client's server configuration, for example:

{
  "mcpServers": {
    "nimbus": {
      "command": "npx",
      "args": ["-y", "@nimbus-dev/mcp"]
    }
  }
}

Clients that install from the MCP Registry can find this server listed as io.github.nimbus-agent/nimbus.

Running from a local checkout

To run the launcher straight from a clone of this repository — when developing it, or to try a change before it is released — point your MCP client at the entry point itself. Use absolute paths: an editor-spawned MCP server does not inherit your shell's working directory.

{
  "mcpServers": {
    "nimbus": {
      "command": "bun",
      "args": ["/absolute/path/to/nimbus-mcp/src/index.ts"]
    }
  }
}

If you already have the Nimbus CLI installed, you can skip the launcher altogether and have your client run nimbus mcp-server --stdio directly — the launcher exists only to find that binary for you.

How the binary is found

The launcher looks for the Nimbus binary in this order:

Shortened. The full README is on GitHub.