Loading
Nimbus BCI
io.github.nimbusbciClaim this server
Power your agent
Add this server
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Server URL
https://nimbus-mcp.fly.dev/mcpCredentials from the publisher
- NIMBUS_API_URL — Nimbus backend URL. Defaults to the local backend (http://127.0.0.1:8080) — the desktop app and local key flow expect this; use https://nimbus-studio.fly.dev to run against the hosted API.
- NIMBUS_TOKEN — Hosted API token (nimb_…) minted in Nimbus Studio → Account → API tokens. Not needed if you already ran `nimbus-mcp login`.
- NIMBUS_TOKEN_FILE — Path to a 0600 JSON file {"token": "…"} holding a hosted API token (keeps secrets out of MCP configs).
- NIMBUS_MCP_KEY — Local-backend key; must match MCP_LOCAL_KEY on your Nimbus backend (dev server) or the desktop app's key.
- NIMBUS_MCP_KEY_FILE — Path to a local-backend key file. The desktop app's mcp-key.json is auto-discovered without this.
The Claude button above opens Claude with the name and URL filled in. You still confirm it there.
shClaude Code
claude mcp add --transport http io.github.nimbusbci-nimbus-mcp https://nimbus-mcp.fly.dev/mcpRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.nimbusbci-nimbus-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://nimbus-mcp.fly.dev/mcp" ] } }}claude_desktop_config.json
Remote · HTTPPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Remote- Transport
- http
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ