Skip to content

VS Code local intel local_intel_changes

How to: VS Code local intel local_intel_changes

client:VS Code transport:streamable-http tool:local_intel_changes

Add local intel to VS Code

  1. 01

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

{
  "servers": {
    "local-intel": {
      "type": "http",
      "url": "https://gsb-swarm-production.up.railway.app/api/local-intel/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that local intel'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

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.