Cursor Nimbus BCI execution.results
How to: Cursor Nimbus BCI execution.results
Add Nimbus BCI to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"nimbus-mcp": {
"url": "https://nimbus-mcp.fly.dev/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something execution.results does. Cursor lists the server's tools on connect and calls execution.results 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.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Nimbus BCI will not start until these are set, so execution.results 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.