Nimbus MCP Server

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

Packages and local setup

The published npm package is @nimbus-dev/mcp, version 0.4.1. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.4.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.