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:
1. Open your MCP config in Kiro: command palette → **Kiro: Open user MCP config (JSON)**
(or the workspace one, .kiro/settings/mcp.json).
2. Add the server:
3. Provide your Kilter credentials. Either:
- set KILTER_USERNAME and KILTER_PASSWORD as environment variables (Kiro expands
${VAR} after you approve the variables in **Settings → Mcp Approved Env Vars**; see
how to set them on macOS, Linux and Windows), or
- replace the ${...} placeholders with the literal values. Only do this in the *user*
config (~/.kiro/settings/mcp.json), never in a workspace config you might commit.
4. 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 KILTER_USERNAME=... --env KILTER_PASSWORD=....
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
Tools the agent gets
| Tool | What it returns |
|---|---|
| kilter_get_logs | Logbook entries (filter by limit, angle, topped, date range) |
| kilter_get_sends | Topped climbs, newest first |
| kilter_get_projects | Climbs attempted but never topped at that angle |
| kilter_get_summary | Totals, angles, date range, hardest send/flash, sends by grade |
| kilter_get_grade_pyramid | Sends per grade with flash rates |
| kilter_get_hardest_sends | Hardest unique sends |
| kilter_get_sessions | Entries grouped by day |
| kilter_get_progression | Month-by-month or week-by-week trend |
| kilter_get_angle_stats | Per-angle comparison |
All tools are read-only and only ever see the account whose credentials you configured.