intervals-icu-mcp

A read-only MCP (Model Context Protocol) server for Intervals.icu.
Gives any MCP-compatible AI assistant access to your activities, wellness data, fitness curves, training zones, and calendar.

Compatible with any client that supports the MCP protocol, including Claude (Desktop, Code, and Web), Cursor, Windsurf, and others.

Available Tools

| Tool | Description | |---|---| | get_athlete | Profile, FTP, weight, VO2max, thresholds | | get_athlete_zones | Power, HR and pace training zones | | get_athlete_gear | Bikes, shoes and usage stats | | get_training_plan | Currently assigned training plan | | list_activities | Activities list with date range and sport type filters | | get_activity | Full activity detail + detected intervals | | get_activity_streams | Raw second-by-second data (power, HR, cadence, altitude…) | | get_activity_power_curve | Mean maximal power (MMP) curve | | get_fitness | CTL/ATL/TSB fitness curve over a date range | | list_wellness | Daily wellness entries over a date range (HRV, sleep, weight, mood…) | | get_wellness | Single-day wellness entry | | list_calendars | All calendars configured for the athlete | | list_events | Calendar events with date range and category filter | | get_event | Single calendar event by ID |

Prerequisites

• Node.js v18 or later
• An Intervals.icu account with an API key

Get your API key:

1. Log in to intervals.icu
2. Go to Settings → scroll down to Developer Settings
3. Generate (or copy) your API Key

Installation

No installation needed — npx downloads and runs the package automatically.

Add the following to your MCP client config, replacing your_api_key_here with your key:

{
  "mcpServers": {
    "intervals-icu": {
      "command": "npx",
      "args": ["-y", "intervals-icu-mcp"],
      "env": {
        "INTERVALS_API_KEY": "your_api_key_here",
        "INTERVALS_ATHLETE_ID": "0",
        "TRANSPORT": "stdio"
      }
    }
  }
}

INTERVALS_ATHLETE_ID can be left as 0 — the API resolves it automatically from your key.

Config file locations:

| Client | Config file | |---|---| | Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json | | Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json | | Cursor | .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally | | Windsurf | ~/.codeium/windsurf/mcp_config.json |

After editing the config, fully restart your client.

Claude Code (CLI)

claude mcp add intervals-icu \
  -e INTERVALS_API_KEY=your_api_key_here \
  -e INTERVALS_ATHLETE_ID=0 \
  -e TRANSPORT=stdio \
  -- npx -y intervals-icu-mcp

Environment variables

| Variable | Required | Default | Description | |---|---|---|---| | INTERVALS_API_KEY | ✅ | — | Your Intervals.icu API key | | INTERVALS_ATHLETE_ID | — | 0 | Your athlete ID (0 = auto-resolved from key) | | TRANSPORT | — | http | stdio for local clients, http for Docker/remote | | PORT | — | 3000 | HTTP port (Docker/remote mode only) |

Example prompts

"Show me my last 10 cycling activities"
"What was my CTL/ATL trend over the past 3 months?"
"Get the power curve for activity i132547490"
"How did my HRV look last week?"
"What are my current power training zones?"
"List my planned workouts for the next 2 weeks"
"What bikes do I have configured?"
"Show me today's wellness entry"

Development

See DEVELOPMENT.md for instructions on running locally, using Docker, and contributing.

License

MIT