Futureweb Intervals MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add intervals-mcp-server -- uvx futureweb-intervals-mcp

{
  "mcpServers": {
    "intervals-mcp-server": {
      "args": [
        "futureweb-intervals-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.intervals-mcp-server]
command = "uvx"
args = ["futureweb-intervals-mcp"]

{
  "mcpServers": {
    "intervals-mcp-server": {
      "args": [
        "futureweb-intervals-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "intervals-mcp-server": {
      "args": [
        "futureweb-intervals-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: API_KEY (Intervals.icu API key (Settings > Developer Settings)), ATHLETE_ID (Intervals.icu athlete ID), MCP_PERMISSIONS (Enabled tool classes: read (default, read-only), read,write, or all (adds destructive and admin tools)), MCP_TOOLSET (full (every tool of the enabled classes) or core (curated coaching set)), ATHLETE_TIMEZONE (Time zone for 'today' and default date ranges, e.g. Europe/Vienna; default: the Intervals.icu athlete profile). The author declared them in the registry entry; get the values from the project itself.