pipeline.validate_node — Nimbus BCI MCP Tool
pipeline.validate_node
(pipeline validate node) 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 pipeline.validate_node from your client
- Claude Code Nimbus BCI pipeline.validate_node run in your project directory
- Claude Desktop Nimbus BCI pipeline.validate_node ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nimbus BCI pipeline.validate_node ~/.cursor/mcp.json
- VS Code Nimbus BCI pipeline.validate_node .vscode/mcp.json
- Zed Nimbus BCI pipeline.validate_node ~/.config/zed/settings.json
- Windsurf Nimbus BCI pipeline.validate_node ~/.codeium/windsurf/mcp_config.json
- Cline Nimbus BCI pipeline.validate_node ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nimbus BCI pipeline.validate_node ~/.gemini/settings.json
- Grok Nimbus BCI pipeline.validate_node .mcp.json (in your project root)
- ChatGPT Nimbus BCI pipeline.validate_node Settings → Connectors → Advanced → Developer mode
- Claude.ai Nimbus BCI pipeline.validate_node Settings → Connectors → Add custom connector
- LangChain Nimbus BCI pipeline.validate_node 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
- 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.