MCP server · Self-hosted or hosted

Self-hosted
or hosted.

An Intervals.icu MCP server lets an AI assistant read your training. There are two kinds: open-source servers you run yourself, and hosted ones like IntervalSync. Both can answer the same questions about your training. They differ in what you install, which credential you keep, where the server runs, and which assistants can reach it.

This page compares IntervalSync with two open-source servers that people search for by name, using what each project's own README says.

The servers

What each one needs.

SELF-HOSTED / GPL-3.0

mvilanova/intervals-mcp-server

Python 3.12 or higher and uv: you clone the repository, create a virtual environment and install its dependencies. Your Intervals.icu API key and athlete ID go in a .env file. Claude Desktop starts it on your computer from its config file, and you update it with git pull and uv sync. For ChatGPT, its README runs it in SSE mode behind a public URL, for example an ngrok tunnel, with the connector's authentication left as "No authentication" unless you protect the tunnel. It lists sixteen tools, including ones that create, update and delete calendar events and custom items.

Its README on GitHub

SELF-HOSTED / MIT

hhopke/intervals-icu-mcp

A continuation of eddmann/intervals-icu-mcp. It needs uv, whose uvx fetches the package when your client starts it; it can also run from source or in Docker. Your API key and athlete ID go in the client's config, or in a .env file when it runs from source. It runs on your computer over stdio for Claude Desktop, Claude Code and Cursor. It also has HTTP and SSE transports, and its README warns that MCP has no built-in authentication, so an HTTP server needs a tunnel or an authenticating proxy. It lists 70 tools, 4 resources and 9 prompts, and deletes are gated by a setting.

Its README on GitHub

HOSTED / INTERVALSYNC

IntervalSync

Nothing to install: you add one URL to your assistant and sign in with your Intervals.icu account, so no API key is kept in a file. Each assistant gets its own short-lived, revocable token. It runs on servers operated by Walloris Tech LLC, which is what lets assistants on the web and on a phone reach it. It has eighteen read tools, and four tools that change your Intervals.icu data, each only after you confirm. Its code is not public, and full access is a paid plan after a 14-day trial; Free reads once per tool per day.

The MCP server page

Side by side

Where they differ.

QuestionSelf-hosted, as both READMEs describe itIntervalSync

What you installuv, and the server, from a clone, a package or a Docker image.Nothing.

CredentialYour Intervals.icu API key and athlete ID, in a file on your computer.An Intervals.icu sign-in (OAuth). The assistant gets a revocable token, not your key.

Where it runsOn your computer, started by the assistant's desktop app or command line.On IntervalSync's servers.

Who can reach itDesktop clients on that computer. An assistant on the web or a phone needs a public URL, which you set up and protect yourself.Any assistant that supports remote MCP, on the web, the desktop or a phone.

CodeOpen source: GPL-3.0 and MIT.Not public.

CostNo charge from the projects.Free reads once per tool per day after the trial; full access is a paid plan.

When to run your own

When a self-hosted server is the better answer.

You use a desktop client, such as Claude Desktop, Claude Code or Cursor, on one computer, and you are comfortable with uv and a config file.
You want no service between your assistant and Intervals.icu, and your API key to stay on your own computer.
You want to read or change the code.
You want a tool IntervalSync does not have: both READMEs list tools for Intervals.icu's custom items, and hhopke/intervals-icu-mcp lists a workout library and gear.
You do not want to pay for one.

When hosted fits

When a hosted server is the better answer.

Your assistant is in a browser or on a phone: Claude on the web, ChatGPT, Gemini or Grok reach a server over the internet, and a hosted one needs no tunnel of yours.
You would rather sign in with Intervals.icu than keep an API key in a file, and revoke one assistant without touching the others.
You do not want a process running on your computer, or a server and a tunnel to keep up to date.
You want a coach to read your training, or a team to read each other's, by each person's agreement.

The Intervals.icu MCP server has IntervalSync's tools and the setup for each assistant, and pricing has its plans.