Skip to content

VS Code Nimbus BCI execution.get

How to: VS Code Nimbus BCI execution.get

client:VS Code transport:streamable-http tool:execution.get

Add Nimbus BCI to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "nimbus-mcp": {
      "type": "http",
      "url": "https://nimbus-mcp.fly.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something execution.get does. VS Code lists the server's tools on connect and calls execution.get itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Nimbus BCI's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Nimbus BCI will not start until these are set, so execution.get 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.