Strava MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key (get one at https://cotlet.dev/app). Used as the Bearer token for the hosted server; without it, tool calls fail with "Set COTLET_API_KEY." |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Strava through Cotlet.dev. Call strava_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| strava_guideA | How to work in Strava (list activities and update gear): its screens and the sign-in link. Call this first. |
| strava_statusA | Check that your Cotlet.dev account and Strava are ready: account, credits and Strava connection. |
| strava_openB | Open a Strava page in your signed-in Cloud Browser (default https://www.strava.com) to work with list activities and update gear. |
| strava_readA | Read the current Strava page: its text and numbered buttons, links and fields. |
| strava_clickB | Click a numbered element on the current Strava page. |
| strava_typeB | Type text into a numbered field on the current Strava page. |
| strava_closeA | Close the Strava browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a distinct step in a browser-automation lifecycle: guide, status check, open, read, click, type, close. There is no meaningful overlap between them, and the workflow ordering is explicit (guide first, close last).
All seven tools use the same strava_ prefix followed by a short lowercase verb or noun (guide, status, open, read, click, type, close). The pattern is uniform and immediately readable as a single coherent family.
Seven tools is a tight, well-scoped set for driving a signed-in browser session against one site. Every tool corresponds to a necessary primitive in that loop, with no redundant affordances.
The surface covers the essential interaction loop: orient (guide/status), navigate (open), inspect (read), act (click/type), and clean up (close). Minor gaps exist—no explicit scroll, back/navigation, wait-for-load, or file/upload helper—which an agent can usually work around by re-reading the page.