stream.status — Nimbus BCI MCP Tool
stream.status
(stream status) is one of 32 tools on the
Nimbus BCI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call stream.status from your client
- Claude Code Nimbus BCI stream.status run in your project directory
- Claude Desktop Nimbus BCI stream.status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nimbus BCI stream.status ~/.cursor/mcp.json
- VS Code Nimbus BCI stream.status .vscode/mcp.json
- Zed Nimbus BCI stream.status ~/.config/zed/settings.json
- Windsurf Nimbus BCI stream.status ~/.codeium/windsurf/mcp_config.json
- Cline Nimbus BCI stream.status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nimbus BCI stream.status ~/.gemini/settings.json
- Grok Nimbus BCI stream.status .mcp.json (in your project root)
- ChatGPT Nimbus BCI stream.status Settings → Connectors → Advanced → Developer mode
- Claude.ai Nimbus BCI stream.status Settings → Connectors → Add custom connector
- LangChain Nimbus BCI stream.status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nimbus-mcp https://nimbus-mcp.fly.dev/mcpOther tools on this server
- account.whoami
- catalog.nodes
- catalog.node_schema
- catalog.templates
- catalog.template
- catalog.datasets
- catalog.leaderboard
- pipeline.validate
- pipeline.validate_node
- execution.run
- execution.cancel
- execution.get
- execution.list
- execution.results
- experiment.run
- experiment.get
- execution.artifacts
- execution.download_artifact
- pipeline.export
- device.list
- device.test
- stream.start
- stream.stop
- stream.telemetry
- data.upload
- data.inspect_dataset
- data.inspect_file
- project.create
- project.list
- project.save
- project.load
This list was read from the server itself, by connecting to it and calling tools/list on 5 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.