Kilter Board Logbook MCP server

kilter-mcp

<!-- mcp-name: io.github.wmmg101/kilter-mcp -->

An unofficial MCP server that lets your AI agent read and analyse your own Kilter Board logbook.

Add it to Kiro (or another MCP client), give it your Kilter login, and then just talk to the agent:

How did my last Kilter session go?

What are my current projects at 30°?

Compare my climbing at 20° and 40°.

Show my grade pyramid. What are my hardest sends? Am I progressing?

Read-only. Nothing is written to your Kilter account.

Add to Kiro + Other Clients (Claude, Codex, Cursor etc.)

Click the button (Kiro shows a confirmation dialog first), then jump to step 3. Or do it by hand:

(or the workspace one, .kiro/settings/mcp.json).

1. Open your MCP config in Kiro: command palette → Kiro: Open user MCP config (JSON)

1. Add the server:

{
  "mcpServers": {
    "kilter": {
      "command": "uvx",
      "args": ["kilter-mcp"],
      "env": {
        "KILTER_USERNAME": "${KILTER_USERNAME}",
        "KILTER_PASSWORD": "${KILTER_PASSWORD}"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

1. Provide your Kilter credentials. Either:

${VAR} after you approve the variables in Settings → Mcp Approved Env Vars; see how to set them on macOS, Linux and Windows), or

• set KILTERUSERNAME and KILTERPASSWORD as environment variables (Kiro expands

config (~/.kiro/settings/mcp.json), never in a workspace config you might commit.

• replace the ${...} placeholders with the literal values. Only do this in the user

1. Save. Kiro starts the server and the kilter_* tools appear. Ask away.

Something not working? With the same variables exported in a terminal, run uvx kilter-mcp --check. It logs in, counts your logbook and prints a short report with no secrets or entries in it, which you can paste into an issue.

Requirements: uv installed (uvx comes with it). Python is handled by uv.

Kiro CLI users can do the same with kiro-cli mcp add --name kilter --scope global --command uvx --args kilter-mcp --env KILTERUSERNAME=... --env KILTERPASSWORD=....

Optional: timezone

Sessions are grouped by calendar day in your timezone, which is detected from the machine running the server. If that is wrong (for example a remote or containerised host), add "KILTER_TIMEZONE": "Europe/Rome" (any IANA name) to the env block. Every response states the timezone it used.

Other clients

kilter-mcp is a standard local MCP server, so it also works in Claude Desktop, Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and Zed. Copy-paste configs for each are in docs/clients.md. (ChatGPT's chat interface only accepts remote HTTP servers, so it is not supported directly; details in the same document.)

Example questions

Show my latest Kilter session.
What did I climb last Saturday?
List my sends from this month at 40°.
What are my current projects?
Which projects have I put the most attempts into?
Show my grade pyramid at 30°.
What is my flash rate per grade?
What are my five hardest sends?
Compare my climbing at 20° and 30°.
How has my climbing progressed over the last six months?

Tools the agent gets

Shortened. The full README is on GitHub.