Boardsesh Climbing Logbook

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/wmmg101-boardsesh-mcp

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

12 read · 0 write · 0 deleteRead-only

Secrets

2 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Python package

Tools (12)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• boardsesh_compare_boards

  Compare the user's climbing across every board they have logged on. Use when the user asks which board they are strongest on, how Kilter compares with Tension or MoonBoard, or where they climb most. One row per board with sends, flashes, flash rate, tries, sessions, angles, hardest send in that board's own grades, and 'hardest_boardsesh_grade' / 'median_boardsesh_grade' which are normalised across boards and therefore the fair comparison.

• boardsesh_find_similar_climbs

  Find climbs that use a similar set of holds to a given climb. Use when the user asks for climbs like one they enjoyed or one they are projecting, or wants to train a specific movement again. Similarity is hold overlap (0-1); 0.5 and above feels genuinely related. Pass a climb_uuid from an earlier result.

• boardsesh_get_ascents

  Return the user's logbook entries, newest first, across every board. Use when the user asks about recent climbs, sends, flashes, attempts, what they did on a date, or wants raw history. Each entry is one climb at one angle on one board at one time with the number of tries. Filters: limit (default 25), board, angle, status ('all', 'sends', 'attempts', 'flashes'), start_date/end_date (YYYY-MM-DD).

• boardsesh_get_grade_pyramid

  Return the user's send pyramid: sends per grade, hardest first, with flash rates. Use when the user asks about their pyramid, grade distribution, flash rate per grade, or how solid they are at a level. Optional board filter; grades differ between boards, so prefer filtering to one board when the user names one.

• boardsesh_get_grades

  Return a board's grade scale: difficulty_id to grade label. Use when you need a difficulty_id for a grade the user named (e.g. to pass min_grade_id to a search), or to explain what a grade id means. Boards do not share one scale.

• boardsesh_get_hold_heatmap

  Return which holds the wall's climbs use, for spotting strengths and weaknesses. Use when the user asks about weaknesses, hold types they avoid or overuse, or what to train. Returns per-hold counts (how many climbs use each hold, and whether as hand, foot, start or finish) plus the average difficulty of climbs using it. Combine with a grade range to ask "which holds appear in climbs at my next grade". Hold ids are wall positions; reason about patterns and grade ranges rather than individual ids.

• boardsesh_get_progression

  Return climbing progression over time, oldest period first. Use when the user asks whether they are improving, about trends, or for a month-by-month or week-by-week view. Each period has sessions, boards used, entries, sends, unique climbs, flashes, tries and the hardest send.

• boardsesh_get_projects

  Return the user's projects: climbs attempted but never sent at that angle. Use when the user asks what they are working on, unfinished climbs, or what to try again. A project is per (board, climb, angle), so sending a climb at another angle does not remove it. Sorted by most recently tried, then most tries.

• boardsesh_get_sessions

  Return recent climbing sessions (entries grouped by calendar day), newest first. Use when the user asks how their last session went, what they climbed on a day, or wants to compare sessions. Each session lists the boards and angles used, sends, flashes, total tries, hardest send and every climb logged that day.

• boardsesh_get_summary

  Return a compact overview of the user's whole Boardsesh history, across all boards. Use first for broad questions ("how is my climbing going?", "summarise my logbook") or when you need totals: entries, sends, flashes, tries, boards used, angles, date range, session count, hardest send and flash, and sends per grade.

• boardsesh_recommend_climbs

  Suggest climbs the user has not sent yet, from Boardsesh's recommendations. Use when the user asks what to try next, wants new climbs, projects at their level, or something fresh. 'at_level' works from their own send history and excludes climbs they have already sent. Needs a board configuration, so it uses one of the user's saved Boardsesh boards.

• boardsesh_search_climbs

  Search the board's climb catalogue with filters. Use when the user wants to find specific climbs: by name, grade range, benchmarks only, popularity, or excluding ones they have already sent. For "what should I try next" prefer boardsesh_recommend_climbs, which uses the user's own level.

Signals

Stars

0

Forks

0

Open issues

0

Weekly downloads

29

Last commit

Sep 22, 2026 (1 month ago)

Last release

Sep 22, 2026 (1 month ago)

Last package publish

Sep 22, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.wmmg101/boardsesh-mcp

Version

0.1.0

Auth

API key

Packages

pypi boardsesh-mcp

License

MIT

Repository

github.com/wmmg101/boardsesh-mcp

Website

github.com/wmmg101/boardsesh-mcp

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql