Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Intervals MCP

by ljclversion 2.15.1i★ –iRuns on your computer
Registry nameio.github.ljcl/intervals-mcp

Install

Overview

Description from the maker (original English)

Remote MCP server for intervals.icu run data and analysis

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: INTERVALS_API_KEY, ORS_API_KEY, HOME_START, MCP_AUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: INTERVALS_API_KEY, INTERVALS_ATHLETE_ID, TZ, ORS_API_KEY, HOME_START, MCP_AUTH_TOKEN, PORT, DATA_DIR, ROUTE_RETENTION_DAYS, PUBLIC_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "intervals": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "INTERVALS_API_KEY",
        "-e",
        "INTERVALS_ATHLETE_ID",
        "-e",
        "TZ",
        "-e",
        "ORS_API_KEY",
        "-e",
        "HOME_START",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "DATA_DIR",
        "-e",
        "ROUTE_RETENTION_DAYS",
        "-e",
        "PUBLIC_URL",
        "ghcr.io/ljcl/intervals-mcp:2.15.1"
      ],
      "env": {
        "INTERVALS_API_KEY": "your-value",
        "INTERVALS_ATHLETE_ID": "your-value",
        "TZ": "your-value",
        "ORS_API_KEY": "your-value",
        "HOME_START": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "DATA_DIR": "your-value",
        "ROUTE_RETENTION_DAYS": "your-value",
        "PUBLIC_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add intervals --env INTERVALS_API_KEY=your-value --env INTERVALS_ATHLETE_ID=your-value --env TZ=your-value --env ORS_API_KEY=your-value --env HOME_START=your-value --env MCP_AUTH_TOKEN=your-value --env PORT=your-value --env DATA_DIR=your-value --env ROUTE_RETENTION_DAYS=your-value --env PUBLIC_URL=your-value -- docker run -i --rm -e INTERVALS_API_KEY -e INTERVALS_ATHLETE_ID -e TZ -e ORS_API_KEY -e HOME_START -e MCP_AUTH_TOKEN -e PORT -e DATA_DIR -e ROUTE_RETENTION_DAYS -e PUBLIC_URL ghcr.io/ljcl/intervals-mcp:2.15.1

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "intervals": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "INTERVALS_API_KEY",
        "-e",
        "INTERVALS_ATHLETE_ID",
        "-e",
        "TZ",
        "-e",
        "ORS_API_KEY",
        "-e",
        "HOME_START",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "DATA_DIR",
        "-e",
        "ROUTE_RETENTION_DAYS",
        "-e",
        "PUBLIC_URL",
        "ghcr.io/ljcl/intervals-mcp:2.15.1"
      ],
      "env": {
        "INTERVALS_API_KEY": "your-value",
        "INTERVALS_ATHLETE_ID": "your-value",
        "TZ": "your-value",
        "ORS_API_KEY": "your-value",
        "HOME_START": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "DATA_DIR": "your-value",
        "ROUTE_RETENTION_DAYS": "your-value",
        "PUBLIC_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "intervals": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "INTERVALS_API_KEY",
        "-e",
        "INTERVALS_ATHLETE_ID",
        "-e",
        "TZ",
        "-e",
        "ORS_API_KEY",
        "-e",
        "HOME_START",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "DATA_DIR",
        "-e",
        "ROUTE_RETENTION_DAYS",
        "-e",
        "PUBLIC_URL",
        "ghcr.io/ljcl/intervals-mcp:2.15.1"
      ],
      "env": {
        "INTERVALS_API_KEY": "your-value",
        "INTERVALS_ATHLETE_ID": "your-value",
        "TZ": "your-value",
        "ORS_API_KEY": "your-value",
        "HOME_START": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "DATA_DIR": "your-value",
        "ROUTE_RETENTION_DAYS": "your-value",
        "PUBLIC_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • INTERVALS_API_KEY secret required env
    intervals.icu personal API key (Settings, Developer Settings)
  • INTERVALS_ATHLETE_ID env
    Athlete id: 0 (default, the API key's own athlete) or e.g. i12345
  • TZ env
    IANA time zone for local dates, e.g. Australia/Sydney; unset or UTC follows the athlete's intervals.icu time zone (Etc/UTC pins UTC)
  • ORS_API_KEY secret env
    OpenRouteService API key (openrouteservice.org) for generated route suggestions; unset offers past runs only
  • HOME_START secret env
    Usual run start as lat,lng (e.g. 37.79,-122.39); unset infers it from recent GPS runs
  • MCP_AUTH_TOKEN secret env
    Shared secret (32+ characters) gating /mcp and detailed /health (recommended when internet-facing)
  • PORT env
    Server port, 1-65535 (default 3000)
  • DATA_DIR env
    Directory for stored routes (stitch-route, amend-route); the image uses /data, a volume in docker-compose.yml. Default ./data
  • ROUTE_RETENTION_DAYS env
    Days a stored route not read or changed is kept, 1-3650 (default 30)
  • PUBLIC_URL env
    Public URL, used only to warn when /mcp is exposed without MCP_AUTH_TOKEN

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ljcl, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32680 servers in this category
  • Published to the registry more recently than 100% of the other 32680 servers in this category
  • Basic checks equal to or better than 100% of the other 32680 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Intervals MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: INTERVALS_API_KEY, ORS_API_KEY, HOME_START, MCP_AUTH_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.15.1) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

EmbeddedCI BenchPod

by embeddedci-com

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Intervals Extra (intervals-mcp)

A single-user remote MCP server for intervals.icu run data and analysis, with interactive MCP Apps.

All text tools and every MCP App talk to intervals.icu directly and are verified against a real account; see docs/tools.md for the full catalog. Configuration is checked at startup: a bad variable stops the server with a message naming it, and the key's presence is reported on /health.

History. This project began as strava-mcp and was migrated to intervals.icu as its data source; nothing in the server talks to Strava today.

Setup

1. Get an intervals.icu API key
  1. Log in to intervals.icu
  2. Go to Settings, Developer Settings
  3. Copy your personal API key
2. Configure environment
cp .env.example .env

Edit .env with your values:

INTERVALS_API_KEY=your_api_key

All variables are listed in docs/operations.md.

3. Run it

Local development (needs Bun):

bun install

bun run dev

Docker:

docker compose up -d

Prefer the prebuilt image? Pull ghcr.io/ljcl/intervals-mcp:latest, the newest release (also on the MCP registry as io.github.ljcl/intervals-mcp), and point your compose image: at it instead of building; you still supply your own API key. :edge tracks unreleased main. Published images carry SBOM/provenance attestations you can verify; see operations.md.

GET /health reports liveness without spending an intervals.icu API request; with MCP_AUTH_TOKEN it also reports config and rate-limit state. Response shapes and monitoring guidance: operations.md.

Point any client at http://localhost:3000/mcp. Repo layout, task runner, tests, coverage gates, and Storybook workflow: docs/development.md. Agent conventions live in AGENTS.md.

Connecting to AI Tools

Most AI tools (Claude Desktop, Claude Code, etc.) need an HTTPS URL to reach your MCP server. Since the server runs on your local network, you'll need a tunnel to expose it.

Tailscale Funnel (Recommended)

Tailscale Funnel exposes a local port to the internet over HTTPS with no configuration:

tailscale funnel --bg 3000

→ https://your-machine.tail1234.ts.net

Set PUBLIC_URL in your .env to the resulting URL.

Cloudflare Tunnel
cloudflared tunnel --url http://localhost:3000
Securing the endpoint

A tunnel makes /mcp reachable by anyone who discovers the URL, so they can use the intervals.icu API key configured on the server (the key itself is never exposed to them). Set MCP_AUTH_TOKEN to a long random secret (openssl rand -hex 32) and every /mcp request requires Authorization: Bearer ; each client snippet below shows where the header goes. The secret also gates the detailed half of /health. Full details: operations.md.

Set it in .env alongside your API key; docker-compose.yml forwards it automatically.

AI Tool (Claude Desktop, Claude Code, etc.)

│ HTTPS HTTPS Tunnel (Tailscale / Cloudflare) │ HTTP (localhost:3000) intervals-mcp Server (Docker / Bun) │ HTTPS intervals.icu API

Client configuration

The server works with any MCP client that supports the Streamable HTTP transport. In every snippet below, replace https://your-public-url with your tunnel URL (or http://localhost:3000 for local development), and include the Authorization header only if you set MCP_AUTH_TOKEN.

Claude Desktop

Add to your Claude configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{

"mcpServers": { "intervals-mcp": { "type": "url", "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

Restart Claude Desktop to load the new configuration.

Claude Code
claude mcp add --transport http intervals-mcp https://your-public-url/mcp \

--header "Authorization: Bearer your-mcp-auth-token"

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{

"mcpServers": { "intervals-mcp": { "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

VS Code

Add to .vscode/mcp.json in your workspace (or run MCP: Add Server from the command palette):

{

"servers": { "intervals-mcp": { "type": "http", "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

Other clients (generic Streamable HTTP)

Any client that speaks Streamable HTTP can connect to the /mcp endpoint directly. The endpoint serves the 2026-07-28 revision: clients send stateless requests carrying the io.modelcontextprotocol/* envelope keys and the Mcp-Method/Mcp-Name headers (server/discover advertises capabilities). A 2025-era client (one that opens with initialize) is served statelessly too, because claude.ai loads MCP Apps that way, but it gets no write tool: update-activity, update-wellness and update-gear need a 2026-07-28 client. POST JSON-RPC messages with an Accept: application/json, text/event-stream header. Protocol details: docs/architecture.md.

Tools

The full tool catalog, prompts, permission behaviour, and example requests live in docs/tools.md. All text tools and every MCP App's data handler talk to intervals.icu directly.

Documentation

DocContents
docs/tools.mdFull tool catalog, prompts, permission behaviour, example requests
docs/operations.mdEnvironment variables, the API key, health endpoint, rate limits, endpoint security
docs/architecture.mdServer architecture: transport, HTTP layer, cache, error taxonomy, analysis math
docs/api-notes.mdCalling the intervals.icu API: auth, endpoints, verified behaviour from Phases 1 and 2
docs/mcp-apps.mdMCP App packages: shared shell, mobile, theming, per-app details
docs/development.mdMonorepo mechanics: Turborepo, coverage gates, Storybook gates, Docker build
docs/releasing.mdRelease automation: Conventional Commit PR titles, release-please, publishing
docs/project.mdIssue tracking and project board
docs/Intervals_MCP_Server.mdCapability reference to upload as project knowledge in a Claude project using this server

PRs are squash-merged and the PR title becomes the commit on `main`, so write it as a Conventional Commit (fix: patch, feat: minor, any ! or BREAKING CHANGE: footer major; chore:/docs:/refactor:/ci: release nothing). A CI check rejects non-conforming titles; see docs/releasing.md.

Troubleshooting

Server exits at startup: The message names the variable to fix, one line per bad variable. See operations.md.

AI tool can't reach the server — MCP requires an HTTPS URL. Use a tunnel (Tailscale Funnel or Cloudflare Tunnel) to expose your local server. See Connecting to AI Tools.

API key errors: Check /health first: api_key_configured tells you whether the server has a key set at all. If api_key_configured is true but calls still fail, the key may be wrong or revoked; generate a new one at intervals.icu, Settings, Developer Settings, and update INTERVALS_API_KEY. See operations.md.

Today's run is missing, or dates are a day off: Check time_zone and time_zone_source on /health. With TZ unset (or UTC), the server uses your intervals.icu time zone; set TZ to choose one. See operations.md.

"Cloudflare … answered with a challenge": Cloudflare, in front of intervals.icu, stopped the request before it reached intervals.icu, so this is not an API key problem. Wait a few minutes and retry. See operations.md.

Client can't connect (401 or unsupported protocol version): Each refused /mcp request writes one mcp_rejected line to the server log with its status, JSON-RPC code and, when the client sent it, its name. A 401 means the bearer token is missing or wrong. Code -32022 means the client's envelope names an MCP revision the server does not serve. See operations.md.

Is the server up and reachable? curl https://your-public-url/health. It answers without touching the intervals.icu API, so it works even when your rate limit is exhausted.

Client re-prompts for read tools after I granted them — A release likely renamed a tool or changed its input schema; grants are stored per tool identity, so that drops the grant. Releases say so in the changelog. Otherwise persistence lives in the client — check both connector-level and per-tool settings. See docs/tools.md.

License

MIT

Ask PopNx