Chronicle MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        return subprocess.run(args, check=False, capture_output=True, text=text, errors="replace" if text else None, timeout=timeout)

      <div class="inline"><label class="field">Harness<select data-change="export-harness">${harnesses.map((item) => `<option value="${item.id}" ${item.id === chosen.id ? "selected" : ""}>${esc(item.name)}</option>`).join("")}</select></label><a class="btn primary" href="${href("…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 chronicle -- uvx chronicle-context

{
  "mcpServers": {
    "chronicle": {
      "command": "uvx",
      "args": [
        "chronicle-context"
      ]
    }
  }
}

[mcp_servers.chronicle]
command = "uvx"
args = ["chronicle-context"]

{
  "mcpServers": {
    "chronicle": {
      "command": "uvx",
      "args": [
        "chronicle-context"
      ]
    }
  }
}

{
  "servers": {
    "chronicle": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "chronicle-context"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: CHRONICLE_HOME (Folder for the database and screenshots (default ~/.chronicle)), CHRONICLE_DISABLE_CAPTURE (Set to 1 so this process serves context but never records).