Intervals Icu Mcp
Pull Intervals.icu training, wellness, and performance data into your agent when you build coaching dashboards, automations, or personal fitness tooling.
Overview
io.github.hhopke/intervals-icu-mcp is a Build-phase MCP server that connects agents to Intervals.icu training, wellness, and performance data via API key authentication.
What is this MCP server?
- MCP access to Intervals.icu training, wellness, and performance datasets
- Python package intervals-icu-mcp v3.0.0 with stdio transport
- Requires INTERVALS_ICU_API_KEY and INTERVALS_ICU_ATHLETE_ID env vars
- Lets LLMs summarize workouts, load, and wellness without scraping the web UI
- Useful for indie coaching apps, personal agents, and athlete-facing SaaS prototypes
- Package intervals-icu-mcp version 3.0.0 (PyPI)
- Required env: INTERVALS_ICU_API_KEY, INTERVALS_ICU_ATHLETE_ID
- Transport: stdio MCP
Community signal: 15 GitHub stars.
What problem does it solve?
Building an agent or app around Intervals.icu data forces you to context-switch between the training site and your editor to copy workouts and wellness metrics.
Who is it for?
Solo developers and athlete-coaches shipping Intervals.icu-connected tools, bots, or personal automation on MCP-capable agents.
Skip if: Builders without Intervals.icu accounts, generic fitness apps on other platforms only, or teams needing real-time medical device integrations.
What do I get? / Deliverables
After configuring API key and athlete ID, your agent can query Intervals.icu training and wellness data through MCP while you implement features.
- MCP tool access to Intervals.icu training, wellness, and performance endpoints for your athlete
- Agent-readable summaries of workouts and load for app or bot features
- Faster integration prototyping without custom scrapers
Recommended MCP Servers
Journey fit
Build integrations is the primary shelf for niche sports-data MCP servers that wire a third-party API into agent-driven products. integrations fits API-key-backed MCP bridges to Intervals.icu rather than generic frontend or docs work.
How it compares
Intervals.icu sports-data MCP integration, not a general health analytics warehouse.
Common Questions / FAQ
Who is io.github.hhopke/intervals-icu-mcp for?
It is for developers and coaches who use Intervals.icu and want LLM agents to access training, wellness, and performance data over MCP.
When should I use io.github.hhopke/intervals-icu-mcp?
Use it while building or extending apps, dashboards, or agent workflows that need live Intervals.icu athlete data during implementation.
How do I add io.github.hhopke/intervals-icu-mcp to my agent?
Install intervals-icu-mcp from PyPI, set INTERVALS_ICU_API_KEY and INTERVALS_ICU_ATHLETE_ID in MCP stdio config, and restart your agent client.