Claude Desktop Nimbus BCI execution.artifacts
How to: Claude Desktop Nimbus BCI execution.artifacts
Add Nimbus BCI to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"nimbus-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://nimbus-mcp.fly.dev/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something execution.artifacts does. Claude Desktop lists the server's tools on connect and calls execution.artifacts itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Nimbus BCI's identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Nimbus BCI will not start until these are set, so execution.artifacts never becomes available.
-
NIMBUS_API_URL -
NIMBUS_TOKEN -
NIMBUS_TOKEN_FILE -
NIMBUS_MCP_KEY -
NIMBUS_MCP_KEY_FILE
Same tool, other clients
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.