Intervals MCP Server

Model Context Protocol (MCP) server for connecting Claude and ChatGPT with the Intervals.icu API. It provides tools for authentication and data retrieval for activities, events, wellness data, power curves, and custom items. That is what the intervals mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 4 tools. What each one is for:

• Name — Intervals.icu
• Authentication — leave as No authentication unless you have protected your tunnel
• Troubleshooting — If Claude Desktop fails due to configuration changes, follow these steps:
• Windows — The mcp install command may fail on Windows due to environment or permission issues. Instead, configure Claude Desktop manually:

What it needs from you

Configuration is passed through the environment: INTERVALS_API_BASE_URL, ATHLETE_ID, API_KEY, LOG_LEVEL, FASTMCP_HOST, YOUR_ATHLETE_ID, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.12 or higher - Model Context Protocol (MCP) Python SDK - httpx - python-dotenv

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Intervals's toolset — Name, Authentication, Troubleshooting and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mvilanova; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.