Nimbus BCI MCP Server

AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions.

Local + remotestreamable-httpstdio

What is the Nimbus BCI MCP Server?

Nimbus BCI is an MCP integration. AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions.

Hosted connection

The registry lists a streamable-http connection at https://nimbus-mcp.fly.dev/mcp.

Packages and local setup

The published pypi package is nimbus-mcp, version 0.10.0. Its declared MCP transport is stdio.

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

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.10.0 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 other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
NIMBUS_API_URLNimbus 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.Check documentation
NIMBUS_TOKENHosted API token (nimb_…) minted in Nimbus Studio → Account → API tokens. Not needed if you already ran nimbus-mcp login.Check documentation
NIMBUS_TOKEN_FILEPath to a 0600 JSON file {"token": "…"} holding a hosted API token (keeps secrets out of MCP configs).Check documentation
NIMBUS_MCP_KEYLocal-backend key; must match MCP_LOCAL_KEY on your Nimbus backend (dev server) or the desktop app's key.Check documentation
NIMBUS_MCP_KEY_FILEPath to a local-backend key file. The desktop app's mcp-key.json is auto-discovered without this.Check documentation