state-trace MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add state-trace -- uvx state-trace

{
  "mcpServers": {
    "state-trace": {
      "args": [
        "state-trace"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.state-trace]
command = "uvx"
args = ["state-trace"]

{
  "mcpServers": {
    "state-trace": {
      "args": [
        "state-trace"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "state-trace": {
      "args": [
        "state-trace"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: STATE_TRACE_STORAGE_PATH (Path to the SQLite or JSON file backing the working-memory graph. .db/.sqlite/.sqlite3 = SQLite (recommended); other = JSON. Defaults to ~/.state-trace/memory.db.), STATE_TRACE_NAMESPACE (Namespace to scope reads and writes (e.g. the repo slug). Nodes without a namespace remain visible to all namespaces.), STATE_TRACE_CAPACITY_LIMIT (Working-memory budget in capacity units. Default 256.). The author declared them in the registry entry; get the values from the project itself.