Nimbus

Name: Nimbus
Author: nimbus-agent

by nimbus-agentversion 0.4.1i★ –iRuns on your computer

Registry nameio.github.nimbus-agent/nimbus

Install

Overview

Description from the maker (original English)

Search your local Nimbus index and run its built-in agents from any MCP client.

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: Search & AI memory

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).
You fill in yourself: NIMBUS_BIN, NIMBUS_MCP_TIMEOUT_MS

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": {
    "nimbus": {
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ],
      "env": {
        "NIMBUS_BIN": "your-value",
        "NIMBUS_MCP_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add nimbus --env NIMBUS_BIN=your-value --env NIMBUS_MCP_TIMEOUT_MS=your-value -- npx -y @nimbus-dev/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "nimbus": {
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ],
      "env": {
        "NIMBUS_BIN": "your-value",
        "NIMBUS_MCP_TIMEOUT_MS": "your-value"
      }
    }
  }
}

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": {
    "nimbus": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ],
      "env": {
        "NIMBUS_BIN": "your-value",
        "NIMBUS_MCP_TIMEOUT_MS": "your-value"
      }
    }
  }
}

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.

Values you fill in

NIMBUS_BIN env
Optional absolute path to the nimbus binary. Only needed when the launcher cannot find it on PATH or in a known install directory — most commonly a GUI-launched editor on macOS, which spawns MCP serv…
NIMBUS_MCP_TIMEOUT_MS env
Optional. How long the Nimbus CLI's MCP adapter waits for an agent brief before returning a clean timeout error; defaults to 60000. Lower it when your client's own MCP transport timeout is shorter, s…

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 nimbus-agent, 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 Search & AI memoryi

More stars than 0% of the other 7271 servers in this category
Published to the registry more recently than 33% of the other 7271 servers in this category
Basic checks equal to or better than 100% of the other 7271 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 Nimbus 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.4.1) reached the registry 2 months 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: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

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.

@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 and running. 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). Start the gateway with nimbus start: the MCP server comes up without it, but its tool calls then return an error asking you to start it.

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:

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 Nimbus monorepo (packages/cli, packages/gateway). A tool that is missing or misbehaving is a bug there, not here.
Parse, filter, proxy, or rewrite the MCP stream. The child process inherits stdio, and traffic passes through untouched in both directions.
Manage gateway configuration, authentication, or the index itself. Configure those the way you normally do; this launcher passes your environment through unchanged and otherwise stays out of the way.
Take on runtime dependencies. package.json has devDependencies only. That is a licence and supply-chain boundary rather than a style preference — adding a runtime dependency here is a deliberate decision, not a convenience call.

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:

NIMBUS_BIN — an explicit full path to the binary, if set. A NIMBUS_BIN that points at a non-existent file is reported as an error, never silently ignored.
PATH — the first nimbus (or nimbus.exe on Windows) found on your PATH.
Known per-platform install directories, the installer's own output directory first, then the directories the other Nimbus distribution channels write to:

Platform	Searched in order
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`
macOS	`~/.local/bin` (installer and `.pkg`), then `/opt/homebrew/bin` and `/usr/local/bin` (Homebrew)
Linux	`~/.local/bin` (installer), then `/usr/local/bin` (apt/yum) and `/usr/bin`, then `/home/linuxbrew/.linuxbrew/bin` and `~/.linuxbrew/bin` (Homebrew)

Step 3 is what carries a GUI-launched editor on macOS, which typically spawns MCP servers without your shell's PATH. If none of those resolve, the launcher exits with a message naming the fix — never a bare exit code.

If you installed Nimbus somewhere else entirely, set NIMBUS_BIN rather than waiting for a directory to be added here.

Environment variables

NIMBUS_BIN — override the resolved binary path. Point it at the exact Nimbus CLI executable — on Windows, nimbus.exe itself. Node will not start a .cmd or .bat wrapper without a shell, so one fails with Failed to start the Nimbus MCP server: spawn EINVAL.
NIMBUS_MCP_TIMEOUT_MS — how long the Nimbus CLI's MCP adapter waits for an agent brief before returning a clean timeout error; it defaults to 60 s. Lower it when your editor's own MCP transport timeout is shorter, so the tool reports a timeout instead of having the call severed underneath it. This is the adapter's own budget — the gateway imposes no such timeout. It is read by the underlying nimbus mcp-server process, which this launcher execs with your environment inherited unchanged.

License

MIT — see LICENSE. Note that the Nimbus gateway and CLI this launcher execs are licensed separately under AGPL-3.0.

Nimbus

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

@nimbus-dev/mcp

What this is

Scope

Install

Quickstart

Running from a local checkout

How the binary is found

Environment variables

See also

License