The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Boardsesh Climbing Logbook listing page.
An unofficial MCP server that lets your AI agent read and analyse your Boardsesh climbing logbook — across every board you climb on: Kilter, Tension, MoonBoard, Decoy, Touchstone, So iLL, Woods and spray walls.
How did my last session go? Am I stronger on Kilter or on Tension? What are my projects at 40°? What should I try next at my level? Show my grade pyramid. Which holds do I avoid?
Read-only. Nothing is ever written to your Boardsesh account.
You do not need to give it a password. Boardsesh serves your logbook publicly, so your display name alone unlocks most of it. Credentials are optional and only add the extras.
Open your MCP config (command palette → Kiro: Open user MCP config (JSON)) and add:
That is the whole setup. BOARDSESH_USER is the display name on your Boardsesh profile (or your
user id, if you prefer). Requires uv installed; uvx ships with
it.
Same three facts everywhere: command uvx, args ["boardsesh-mcp"], env BOARDSESH_USER.
Copy-paste configs for Claude Desktop, Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI
and Zed are in docs/clients.md.
Four tools need to know which physical board setup you use (layout, size, hold sets), which Boardsesh only tells the logged-in owner. Add your Boardsesh login to enable them:
Those four are boardsesh_recommend_climbs, boardsesh_search_climbs,
boardsesh_find_similar_climbs and boardsesh_get_hold_heatmap. Everything else works without
them. See how to set environment variables.
Sessions are grouped by calendar day in your timezone, detected from the machine running the
server. If that is wrong, add "BOARDSESH_TIMEZONE": "Europe/Rome" (any IANA name).
Works with just BOARDSESH_USER:
| Tool | What it returns |
|---|---|
boardsesh_get_summary | Totals across all boards: sends, flashes, sessions, date range, hardest send |
boardsesh_get_ascents | Logbook entries, filterable by board, angle, outcome and date range |
boardsesh_get_sessions | Entries grouped by day |
boardsesh_get_projects | Climbs attempted but never sent, per board, climb and angle |
boardsesh_compare_boards | One row per board, with cross-board normalised grades |
boardsesh_get_grade_pyramid | Sends per grade with flash rates |
boardsesh_get_progression | Month-by-month or week-by-week trend |
boardsesh_get_grades | A board's grade scale (difficulty ids to labels) |
Needs BOARDSESH_EMAIL / BOARDSESH_PASSWORD:
| Tool | What it returns |
|---|---|
boardsesh_recommend_climbs | Climbs to try next: at your level, crowd favourites, hidden gems, fresh |
boardsesh_search_climbs | Catalogue search by name, grade range, benchmarks, popularity |
boardsesh_find_similar_climbs | Climbs sharing holds with a given climb |
boardsesh_get_hold_heatmap | Which holds the wall's climbs use, for spotting weaknesses |
status is authoritative: flash (sent first try), send (sent after attempts) or attempt
(not sent). It is never inferred from try counts.(board, climb, angle) you have attempted but not sent. Sending it at another
angle does not remove it.grade is the board's own grade and difficulty_id the raw id. Board grades are not
comparable between boards, so boardsesh_grade — Boardsesh's cross-board normalised number —
is what boardsesh_compare_boards uses. It is null when Boardsesh's confidence in it is not
backed by real ascents.ws.boardsesh.com and www.boardsesh.com. No telemetry.Troubleshooting: run uvx boardsesh-mcp --check with the same environment variables set. It
prints counts and configuration only, no entries and no secrets, so it is safe to paste into an
issue.
Boardsesh is an open-source (Apache-2.0) board-climbing app that aggregates logbooks across boards and publishes an API. This project is an independent MCP client for it, built at the suggestion of its maintainer, but it is not an official Boardsesh product and any bug here is mine, not theirs.
If you only climb on a Kilter Board and do not use Boardsesh, kilter-mcp talks to Kilter directly instead. boardsesh-mcp is the better choice if you use more than one board, because it can compare them.
Issues and pull requests welcome — see CONTRIBUTING.md. Security reports go through SECURITY.md.