mcpbeat Sign in

Nimbus MCP Server

by nimbus-agent Your server? Claim it
local only

Nimbus runs on your own machine — the client starts it, so there is no endpoint to ping. 31 installs a week from npm. Last commit 4 Oct 2026.

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

Installs per day peak 25 · avg 8 · -6% w/w
a month agotoday
31
Installs / week
npm · @nimbus-dev/mcp
0
Stars
0 open issues
4 Oct 2026
Last commit
5 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 4 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command src/index.ts:41
  child = spawn(resolution.path, ["mcp-server", "--stdio"], { stdio: "inherit" });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add nimbus -- npx -y @nimbus-dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nimbus": {
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.nimbus]
command = "npx"
args = ["-y", "@nimbus-dev/mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "nimbus": {
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nimbus": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nimbus-dev/mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: NIMBUS_BIN (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 servers without the user's shell PATH), NIMBUS_MCP_TIMEOUT_MS (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, so the tool reports a timeout instead of having the call severed underneath it. Read by the nimbus mcp-server process the launcher execs, which inherits this environment unchanged).

Alternatives to Nimbus

same job, measured the same way
Callimachus
by betabots-llc

MCP server for Callimachus: local index and search of your AI coding-agent threads

36 installs/wk local only
Designvault
by designvault

Search, browse and manage your DesignVault design-asset library from any MCP client.

22 installs/wk local only
Whatsapp
by wacli

Your own WhatsApp as an MCP server: read, search and send from any MCP client.

answering
Notesbridge
by isaiahdupree

Search, read, and write your Apple Notes from ChatGPT/Claude via a local Mac agent + MCP relay.

answering
Caliu Notes
by caliuapp

Read and write your Caliu notes from any MCP client: search, create, tag, remind, attach files.

59 installs/wk answering
A2asearch MCP
by tadas-github

Search 10,000+ AI agents, MCP servers, and CLI tools via A2ASearch from any MCP client.

54 installs/wk local only
Computer-Use Agents API
by hcompai

Run and manage H Company's Computer-Use Agents from any MCP client.

9 tools answering
Inblog
by inblog

Run your company blog for SEO and AI search from your AI assistant.

answering

Nimbus — questions

Answers built from our own checks of this server.

Why is there no uptime for Nimbus?
Nimbus runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @nimbus-dev/mcp was installed 31 times last week.
How do I connect Nimbus?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @nimbus-dev/mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Nimbus?
The npm package @nimbus-dev/mcp was installed 31 times in the last week. Week over week that is -6%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Nimbus open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.