intervals-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTERVALS_API_KEY | Yes | Your Intervals.icu API key used to authenticate the MCP server. | |
| INTERVALS_DRY_RUN | No | Set to 1 to simulate actions without publishing, or 0 to enable real publishing. | |
| INTERVALS_ATHLETES | Yes | List of authorized athlete aliases/IDs allowed to be accessed by the MCP server. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listar_atletasA | Lista os apelidos de atletas autorizados neste MCP. |
| listar_treinosA | Lista treinos planejados e provas no calendário do atleta entre duas datas (AAAA-MM-DD, até 90 dias). 'criado_pelo_mcp' indica se o treino pode ser alterado/apagado por este MCP. |
| criar_treinoA | Publica um treino planejado no calendário do atleta. Ele sincroniza com o Garmin. data: AAAA-MM-DD (hoje até 120 dias à frente). esporte: Ride, Run, Swim, WeightTraining etc. texto: treino na sintaxe do Intervals.icu, um passo por linha começando com '-'. Só chame depois que o usuário aprovar o treino. |
| atualizar_treinoA | Altera um treino criado por este MCP (data, nome, esporte e/ou texto). Campos omitidos ficam como estão. Só chame depois que o usuário aprovar a alteração. |
| apagar_treinoA | Apaga UM treino futuro criado por este MCP. Só chame depois que o usuário confirmar. |
| atividades_recentesA | Resumo das atividades concluídas nos últimos N dias (1 a 42): duração, FC, carga, tempo em zonas de FC, RPE. Atividades importadas do Strava não aparecem pela API; a atleta precisa sincronizar pelo Garmin. |
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 6 tools
Each tool targets a distinct resource+action pair: listing athletes, listing workouts, and the create/update/delete lifecycle for workouts are clearly separated, with recent activities being the only read-only metrics tool. Descriptions reinforce the boundaries (e.g., only MCP-created workouts can be updated/deleted), leaving no realistic misselection risk.
Five tools follow a clean Portuguese verb_noun pattern (listar_atletas, listar_treinos, criar_treino, atualizar_treino, apagar_treino) with consistent singular/plural handling by resource. atividades_recentes is a noun-only outlier, but the deviation is minor and still readable.
Six tools is well-scoped for an athlete calendar integration: two read/list tools, a full workout mutation set, and one activity summary tool. Every tool earns its place with no redundancy or filler.
Workout coverage is complete for the lifecycle (create, list, update, delete) plus athlete listing and completed-activity summaries, so core agent workflows have no dead ends. Minor gaps exist: no way to fetch a single workout's full details or drill into an individual activity beyond the recent summary.