account.whoami — Nimbus BCI MCP Tool
account.whoami
(account whoami) 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 account.whoami from your client
- Claude Code Nimbus BCI account.whoami run in your project directory
- Claude Desktop Nimbus BCI account.whoami ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nimbus BCI account.whoami ~/.cursor/mcp.json
- VS Code Nimbus BCI account.whoami .vscode/mcp.json
- Zed Nimbus BCI account.whoami ~/.config/zed/settings.json
- Windsurf Nimbus BCI account.whoami ~/.codeium/windsurf/mcp_config.json
- Cline Nimbus BCI account.whoami ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nimbus BCI account.whoami ~/.gemini/settings.json
- Grok Nimbus BCI account.whoami .mcp.json (in your project root)
- ChatGPT Nimbus BCI account.whoami Settings → Connectors → Advanced → Developer mode
- Claude.ai Nimbus BCI account.whoami Settings → Connectors → Add custom connector
- LangChain Nimbus BCI account.whoami pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nimbus-mcp https://nimbus-mcp.fly.dev/mcp
Other tools on this server
- 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.status
- 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.