Claude Desktop Dc Code archive_evidence

How to: Claude Desktop Dc Code archive_evidence

client:Claude Desktop transport:streamable-http tool:archive_evidence

Add Dc Code to Claude Desktop

01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "dc-code": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://gateway.pipeworx.io/dc-code/mcp"
      ]
    }
  }
}

02
Save the file and restart Claude Desktop.
03
Ask for something archive_evidence does. Claude Desktop lists the server's tools on connect and calls archive_evidence 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.

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

Dc Code will not start until these are set, so archive_evidence 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 14 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