kilter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KILTER_PASSWORD | Yes | Your Kilter account password. | |
| KILTER_USERNAME | Yes | Your Kilter account username. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kilter_get_logsA | Return the user's Kilter logbook entries, newest first. Use when the user asks about recent Kilter climbs, attempts, what they climbed on a date, or wants raw history. Each entry is one climb at one wall angle on one date with the number of tries in that entry. Filters: limit (default 25, max 500), angle (degrees), topped (true=only sends, false=only unsuccessful attempts), start_date/end_date (YYYY-MM-DD, inclusive). |
| kilter_get_sendsA | Return climbs the user has topped (sent), newest first. Use when the user asks about their sends, ticks, completed climbs or flashes. Entries with status 'flash' were topped on the first try. Filters: limit (default 25, max 500), angle (degrees), start_date/end_date (YYYY-MM-DD). |
| kilter_get_projectsA | Return the user's projects: climbs attempted but never topped at that wall angle. Use when the user asks what they are working on, unfinished climbs, or what to try next. A climb is a project per (climb, angle); sending it at another angle does not remove it. Sorted by most recently tried, then most attempts. Optional angle filter. |
| kilter_get_summaryA | Return a compact overview of the user's whole Kilter history. Use first when the user asks a broad question ("how is my climbing going?", "summarise my Kilter account") or when you need totals: entries, sends, flashes, attempts, angles climbed, date range, session count, hardest send/flash and sends per grade. |
| kilter_get_grade_pyramidA | Return the user's send pyramid: sends per grade, hardest first, with flash rates. Use when the user asks about their grade pyramid, distribution of grades, flash rate per grade, or how solid they are at a level. Optional wall-angle filter. |
| kilter_get_hardest_sendsA | Return the user's hardest sent climbs (unique per climb and angle), hardest first. Use when the user asks about their hardest sends, best climbs, max grade, or personal bests. Optional wall-angle filter; limit defaults to 10. |
| kilter_get_sessionsA | Return recent climbing sessions (entries grouped by calendar day), newest first. Use when the user asks how their last session went, what they climbed yesterday, or wants to compare sessions. Each session lists angles, sends, flashes, attempts, hardest send and every climb logged that day. limit defaults to 5. |
| kilter_get_progressionA | Return climbing progression over time, oldest period first. Use when the user asks how they have progressed, trends, whether they are improving, or for a month-by-month/week-by-week view. period is 'month' (default) or 'week'. Each period has sessions, sends, unique climbs, flashes, attempts and hardest send/flash. Optional wall-angle filter. |
| kilter_get_angle_statsA | Return per-wall-angle statistics so angles can be compared. Use when the user asks to compare angles (e.g. 20° vs 40°), which angle they climb hardest or most at, or flash rate by angle. One row per angle with sends, flashes, attempts, sessions, hardest send/flash and sends per grade. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct analytical view (sends vs logs vs projects vs sessions), but sends, logs, and hardest_sends overlap in the 'climbed successfully' space. Descriptions clarify the differences well, so confusion is unlikely but possible for an agent searching for a send list.
All tools follow the exact same kilter_get_<noun> pattern, making the naming scheme highly predictable and easy to navigate. No mixed conventions or verb variations exist.
Nine tools is well within the ideal range for a focused analytics server. Each tool covers a distinct query mode without unnecessary bloat or obvious redundancy.
The tool surface covers the key analytical queries for a Kilter climbing history: overall summary, per-angle stats, progression, sessions, projects, sends, and hardest sends. Minor gaps exist such as no per-climb detail view or direct grade-based filtering of send lists, but these are workable via existing tools.