Gemini CLI Dc Code dc_statute

How to: Gemini CLI Dc Code dc_statute

client:Gemini CLI transport:streamable-http tool:dc_statute

Add Dc Code to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "dc-code": {
      "httpUrl": "https://gateway.pipeworx.io/dc-code/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something dc_statute does. Gemini CLI lists the server's tools on connect and calls dc_statute itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Dc Code's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Dc Code will not start until these are set, so dc_statute never becomes available.

PIPEWORX_API_KEY

Same tool, other clients

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

Dc Code MCP server