Intervals Icu MCP vs Ourpr MCP Server
A side-by-side look at the Intervals Icu MCP and Ourpr MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Intervals Icu MCP for sports work as a local process; choose Ourpr MCP Server for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Intervals Icu MCP when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INTERVALS_ICU_API_KEY, INTERVALS_ICU_ATHLETE_ID. - You want tools like
icu_get_recent_activities, icu_get_activities_by_date, icu_get_activity_details.
Choose Ourpr MCP Server when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OURPR_TOKEN, OURPR_API_URL. - You want tools like
ourpr_list_runs, ourpr_get_run, ourpr_run_stream.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 63/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | INTERVALS_ICU_API_KEYINTERVALS_ICU_ATHLETE_ID | OURPR_TOKENOURPR_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 103 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 67 | 11 |
| Full listing | View Intervals Icu MCP | View Ourpr MCP Server |
Tools & capabilities
Intervals Icu MCP tools 67
icu_get_recent_activitiesList the athlete's most recent activities (default last 30 days) — LIGHT summary per item (distance, duration, power, HR, training load). Use for "what have I done recently?", "show last week's rides". For one specific activity by ID use icu_get_activity_details; to search by name/tag use icu_search_activities.icu_get_activities_by_dateList activities within an EXPLICIT date window (oldest..newest) — LIGHT summary per item. Unlike icu_get_recent_activities (anchored to today and capped at 100), this targets an arbitrary historical window and is bounded only by `limit`. Use for "all my runs from June to November 2025", reconstructing training history, or finding the oldest activity in a period. Dates are YYYY-MM-DD. Results are newest-first; if a window holds more than `limit` items, the oldest are dropped first, so widen `limit` (or narrow the window) to reach the very oldest.icu_get_activity_detailsFetch the headline SUMMARY of one activity — name, sport, date, distance, duration, training load, weather, plus all top-level metrics in a single JSON blob. Use for "how was my ride?", "tell me about activity X". For lap-by-lap or per-interval breakdown use icu_get_activity_intervals; for second-by-second time-series use icu_get_activity_streams.icu_search_activitiesSearch activities by name or tag, returning a LIGHT result list — id, name, type, date, distance, time only. Use this first for "find my X" queries. Only escalate to search_activities_full when you specifically need power, HR, training load, or intensity-factor data on the matches (heavier payload).icu_search_activities_fullSearch activities by name or tag, returning FULL Activity objects with power, HR, training load, intensity factor, normalized power, weather — every metric per result. Heavy payload. Use only when the lighter search_activities won't tell you what you need (e.g. "find my threshold rides with NP above 250W").icu_get_activities_aroundFetch the activities chronologically before and after a reference activity (N each side). Use for "what did I do around this race?", training-context queries, progression comparisons.icu_update_activityUpdate an existing activity's metadata (name, type, trainer flag, RPE, feel, etc.). Only fields you pass are sent; everything else stays unchanged.icu_update_activity_streamsUpload raw time-series streams (power, HR, cadence, etc.) onto an existing activity. Destructive — overwrites existing stream data. Accepts JSON array or CSV. Different from get_activity_streams (READ).icu_bulk_create_manual_activitiesBatch-create manual activities (no device upload) with UPSERT on `external_id`. Existing activities with a matching external_id (set by the same OAuth app) are updated; activities without an external_id are always created new.icu_download_activity_fileDownload the original activity file. Downloads the ORIGINAL uploaded file (FIT, TCX, or GPX — whatever the device produced). Different from download_fit_file (forces FIT conversion) and download_gpx_file (forces GPX conversion). If `output_path` is set the file is saved there; otherwise the response embeds base64 content.icu_download_fit_fileDownload activity converted to FIT format (Garmin / most training platforms). Different from download_activity_file (original upload format) and download_gpx_file (GPX format).icu_download_gpx_fileDownload activity converted to GPX format (GPS devices, mapping software). Different from download_activity_file (original upload format) and download_fit_file (FIT format).- +55 more on the listing page
Ourpr MCP Server tools 11
ourpr_list_runsTraining history between two dates, newest first: date, local start, name, type, miles, pace, time, elevation, average heart rate, and on a runs-only list Friel's efficiency factor and the heartbeats each mile took. Start here for totals, streaks, trends, or finding a run. For one run's splits, use ourpr_get_run with an id from here.ourpr_get_runOne activity in full: mile splits with heart rate, cadence, calories, device. Id comes from ourpr_list_runs. For the profile along the route, use ourpr_run_stream.ourpr_run_streamA run's profile on a 10 m grid — elevation, heart rate, power, cadence — as min, average, max and coverage per channel, not every sample. Also each half by distance with its moving pace, heart rate and efficiency, and the drift between them (aerobic decoupling, Pa:HR). No profile is a normal answer for an indoor run.ourpr_run_lapsThe laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile.ourpr_rep_workoutsInterval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs.ourpr_detect_repsWhether one particular run was an interval session, and its reps.ourpr_similar_terrainStretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for.ourpr_training_blocksThe goal race and its Block: race day, distance, goal time, which week of the Block today falls in, and miles for each week. Also the Blocks before past races, each with its result, weeks and peak week. A Block is the race-anchored Monday to Sunday weeks before a race.ourpr_list_racesEvery race ourpr finds in the history, newest first, tune-ups included: date, name, distance, time, pace and run id. Also the fastest result at 5K, 10K, half marathon and marathon among them.ourpr_list_plansThe runner's planned runs between two dates: day, name, miles, time, tag, the runner's note, whether a logged run fulfilled it, and whether ourpr create wrote it. Read it before ourpr_plan_week so a new plan does not land on a day that already holds one.ourpr_plan_weekWrite one planned run, or a week of them, onto days still ahead. Each lands on the runner's week as a plan they can see, edit and remove. Needs a token made with the write scope and ourpr create. Never logs a run.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Intervals Icu MCP
{
"mcpServers": {
"intervals-icu-mcp": {
"command": "uvx",
"args": [
"intervals-icu-mcp"
],
"env": {
"INTERVALS_ICU_API_KEY": "YOUR_INTERVALS_ICU_API_KEY_HERE",
"INTERVALS_ICU_ATHLETE_ID": "YOUR_INTERVALS_ICU_ATHLETE_ID_HERE"
}
}
}
}
Ourpr MCP Server
{
"mcpServers": {
"ourpr-mcp-server": {
"command": "npx",
"args": [
"-y",
"ourpr-mcp-server@0.5.0"
],
"env": {
"OURPR_TOKEN": "YOUR_OURPR_TOKEN_HERE",
"OURPR_API_URL": "YOUR_OURPR_API_URL_HERE"
}
}
}
}
Frequently asked questions
Intervals Icu MCP is categorized under Sports and uses a local stdio subprocess. Ourpr MCP Server belongs to Sports and uses a local stdio subprocess. Pick Intervals Icu MCP for sports work and Ourpr MCP Server for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Intervals Icu MCP has no declared pricing — check the project's own site. Ourpr MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add intervals-icu-mcp and ourpr-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Intervals Icu MCP has a quality signal of 63/100 (Good) with 3 views, 0 installs and 103 GitHub stars. Ourpr MCP Server has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.