Intervals MCP

MCP数据服务

提供方 derrix060

数据服务 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

一个为Intervals.icu训练分析平台提供的动态MCP协议服务器,自动生成并代理所有API工具调用,实现零代码维护和全API覆盖。

一句话选型结论

按资料字段整理

Intervals MCP 属于数据服务类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 2 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

API代理Go本地部署动态工具生成运动数据分析零维护自动认证

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Intervals MCP当前 未标注 未标注 未标注 无 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方derrix060上游标注的维护方 derrix060
分类数据服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

6.8 KB
来自项目仓库与上游目录的原文,未做删改

intervals-mcp

A dynamic MCP (Model Context Protocol) server for Intervals.icu — the training analytics platform for cyclists, runners, and triathletes.

The server reads the Intervals.icu OpenAPI specification at startup, automatically generates 144 tools (as of Feb 2026) covering the entire API, and proxies tool calls to the real API. When the Intervals.icu API changes, simply restart the server to pick up the new endpoints — zero code changes required.

Why

Intervals.icu has a rich API with 146 endpoints covering activities, wellness, workouts, power curves, gear, calendar events, and more. Using it from an LLM requires either hand-writing tool definitions for each endpoint or building a generic proxy.

This server takes the proxy approach: it fetches the official OpenAPI spec, converts every operation into an MCP tool with proper parameter schemas, and handles authentication and athlete ID injection automatically. The result is that any MCP-compatible client (Claude Code, Claude Desktop, etc.) gets full access to your Intervals.icu data without any manual tool definitions.

Benefits

  • Full API coverage — All non-file-upload endpoints are available as tools, generated directly from the official spec
  • Zero maintenance — API changes are picked up on next restart with no code modifications
  • Automatic athlete ID injection — The athleteId parameter is auto-filled on every call, so the LLM never needs to ask for it
  • Format flexibility — Endpoints that support CSV, FIT, or other formats via {ext} are exposed with an optional ext parameter (defaults to JSON)
  • Tag filtering — Expose only the endpoints you need by including or excluding OpenAPI tags
  • Single binary — Built in Go, compiles to a single static binary with no runtime dependencies

Installation

Homebrew (macOS and Linux)```bash

brew tap derrix060/intervals-mcp https://github.com/derrix060/intervals-mcp
brew install intervals-mcp


### With `go install`

Requires Go 1.21 or later.```bash
go install github.com/derrix060/intervals-mcp@latest

This places the binary in your $GOPATH/bin (or $HOME/go/bin by default).

From source```bash

git clone https://github.com/derrix060/intervals-mcp.git
cd intervals-mcp
go build -o intervals-mcp .


## Configuration

The server is configured entirely through environment variables.

| Variable | Required | Description |
|---|---|---|
| `INTERVALS_API_KEY` | Yes | Your Intervals.icu API key |
| `INTERVALS_ATHLETE_ID` | Yes | Your athlete ID (e.g. `i12345`) |
| `INTERVALS_BASE_URL` | No | API base URL (default: `https://intervals.icu`) |
| `INTERVALS_INCLUDE_TAGS` | No | Comma-separated tags to include (e.g. `Wellness,Activities`) |
| `INTERVALS_EXCLUDE_TAGS` | No | Comma-separated tags to exclude |

`INTERVALS_INCLUDE_TAGS` and `INTERVALS_EXCLUDE_TAGS` are mutually exclusive — set one or neither, not both.

### Finding your credentials

1. Log in to Intervals.icu
2. Go to **Settings > Developer Settings**
3. Generate an API key — this is your `INTERVALS_API_KEY`
4. Your athlete ID is shown on the same page (format: `i12345`) — this is your `INTERVALS_ATHLETE_ID`

## Usage with Claude Code

Add to your Claude Code MCP configuration (`~/.claude/claude_desktop_config.json` or via `claude mcp add`):```json
{
  "mcpServers": {
    "intervals-icu": {
      "command": "/path/to/intervals-mcp",
      "env": {
        "INTERVALS_API_KEY": "your-api-key",
        "INTERVALS_ATHLETE_ID": "i12345"
      }
    }
  }
}

Or using the CLI:```bash
claude mcp add intervals-icu /path/to/intervals-mcp \
-e INTERVALS_API_KEY=your-api-key \
-e INTERVALS_ATHLETE_ID=i12345


Once configured, you can ask Claude things like:

- "Show me my recent activities"
- "What's my current fitness summary?"
- "Get my wellness data for this week"
- "List my upcoming workouts"
- "Show my power curve for the last 90 days"

## Usage with Claude Desktop

Add to your Claude Desktop configuration (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):```json
{
  "mcpServers": {
    "intervals-icu": {
      "command": "/path/to/intervals-mcp",
      "env": {
        "INTERVALS_API_KEY": "your-api-key",
        "INTERVALS_ATHLETE_ID": "i12345"
      }
    }
  }
}

Tag filtering

To expose only a subset of the API, use tag filtering. Tags correspond to the sections in the Intervals.icu API docs.

Include only wellness and activity endpoints:```bash
INTERVALS_INCLUDE_TAGS="Wellness,Activities"


Exclude gear-related endpoints:```bash
INTERVALS_EXCLUDE_TAGS="Gear"

Comparison with other Intervals.icu MCP servers

There are several other MCP servers for Intervals.icu. All of them define tools manually, which means they cover only a fraction of the API and require code changes whenever endpoints are added or modified.

Project Language Tools Dynamic? Last updated Status
This project Go 144 Yes 2026-02 Active
mvilanova/intervals-mcp-server Python 6 No 2025-12 Stale
like-a-freedom/rusty-intervals-mcp Rust 57 No 2026-02 Active
eddmann/intervals-icu-mcp Python 48 No 2025-11 Stale
gesteves/domestique TypeScript 43* No 2026-02 Active
patrikmichi/intervals-icu-mcp TypeScript ~30 No 2026-02 New
mrgeorgegray/intervals-icu-mcp TypeScript 12 No 2025-07 Stale
notvincent/Intervals-ICU-MCP TypeScript 4 No 2025-10 Stale

* domestique spans multiple platforms (Intervals.icu + Whoop + TrainerRoad + CORE), so not all 43 tools target Intervals.icu.

Key differences

  • Full API coverage: The most comprehensive hardcoded server has 57 tools. This project exposes 144 — the entire API minus 2 file-upload endpoints that don't make sense for LLM tool use.
  • Zero maintenance: Every hardcoded server falls behind when Intervals.icu adds or changes endpoints. This project reads the official OpenAPI spec at startup, so a restart is all it takes.
  • Tag filtering: No other server lets you include or exclude groups of endpoints via tags.
  • Single binary, no runtime: Like the Rust server, this compiles to a single binary. Unlike the Python and TypeScript servers, there is no interpreter, virtual environment, or node_modules to manage.

How it works

  1. On startup, the server fetches the OpenAPI 3.0 spec from https://intervals.icu/api/v1/docs
  2. Each API operation is converted into an MCP tool using the operationId as the tool name
  3. Path and query parameters become tool input properties with proper JSON Schema types
  4. Request bodies are exposed as a single body parameter
  5. Athlete ID parameters are detected and auto-injected from the environment variable
  6. When the LLM calls a tool, the handler builds an HTTP request, authenticates with Basic Auth, and returns the response

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Intervals MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Intervals MCP 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Intervals MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Intervals MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Intervals MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Intervals MCP 能提供哪些能力?

资料显示能力标签包括 API代理、Go、Claude。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。