state-trace for VS Code

io.github.razroo/state-trace

Bounded working memory for coding agents — typed nodes, current-vs-stale state, MCP-mountable.

client:VS Code transport:stdio runtime:pypi

Install state-trace in VS Code

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "state-trace-storage-path",
      "description": "STATE_TRACE_STORAGE_PATH",
      "password": true
    },
    {
      "type": "promptString",
      "id": "state-trace-namespace",
      "description": "STATE_TRACE_NAMESPACE",
      "password": true
    },
    {
      "type": "promptString",
      "id": "state-trace-capacity-limit",
      "description": "STATE_TRACE_CAPACITY_LIMIT",
      "password": true
    }
  ],
  "servers": {
    "state-trace": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "state-trace"
      ],
      "env": {
        "STATE_TRACE_STORAGE_PATH": "${input:state-trace-storage-path}",
        "STATE_TRACE_NAMESPACE": "${input:state-trace-namespace}",
        "STATE_TRACE_CAPACITY_LIMIT": "${input:state-trace-capacity-limit}"
      }
    }
  }
}

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code docs

state-trace in other clients

state-trace MCP server