Iridium

Provides a bridge to query fitness data like workouts, nutrition, and body measurements via MCP-compatible clients.
  • javascript

0

GitHub Stars

javascript

Language

3 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "rostehea-iridium-mcp-server": {
      "command": "npx",
      "args": [
        "iridium-mcp-server"
      ],
      "env": {
        "IRIDIUM_SYNC_ID": "your-sync-id-here",
        "IRIDIUM_SYNC_KEY": "your-sync-key-here"
      }
    }
  }
}

You can connect Claude or any MCP-compatible client to your Iridium fitness data using the Iridium MCP Server. This server exposes your workouts, nutrition, body measurements, and more in a structured way so you can query and analyze your data directly from your preferred AI assistant.

How to use

After you have the MCP server up and running, you will configure your MCP client (such as Claude Code) to connect to it. You can then request data like workout history, nutrition logs, body measurements, and training metrics. Use natural language queries to fetch summaries, trends, and detailed records, and your client will translate those requests into the appropriate MCP calls.

How to install

Prerequisites you need before installing the MCP server:

  • Node.js 18+

  • Iridium app with AI Data Sync enabled (Settings > AI Data Sync)

Install the MCP server globally or build from source using the commands below.

Step-by-step installation commands

npm install -g iridium-mcp-server

Alternative: build from source

git clone https://github.com/iridium-fitness/iridium-mcp-server.git
cd iridium-mcp-server
npm install
npm run build

Configure Claude Code

Add a configuration block for the Iridium MCP server in Claude Code. The server runs as an MCP instance named iridium and uses your Sync ID and Sync Key from Iridium.

{
  "mcpServers": {
    "iridium": {
      "command": "npx",
      "args": ["iridium-mcp-server"],
      "env": {
        "IRIDIUM_SYNC_ID": "your-sync-id-here",
        "IRIDIUM_SYNC_KEY": "your-sync-key-here"
      }
    }
  }
}

If you built from source

{
  "mcpServers": {
    "iridium": {
      "command": "node",
      "args": ["/path/to/iridium-mcp-server/build/index.js"],
      "env": {
        "IRIDIUM_SYNC_ID": "your-sync-id-here",
        "IRIDIUM_SYNC_KEY": "your-sync-key-here"
      }
    }
  }
}

Available tools

get_workout_history

Fetch recent workout history with optional date range and category filtering.

get_workout_detail

Retrieve full details of a specific workout, including exercises, sets, weights, reps, and RPE.

get_nutrition_log

Get daily nutrition summaries or individual food entries for a specific date.

search_exercises

Search the exercise database by name or muscle group.

get_exercise_progress

Obtain performance history and 1RM trends for a specific exercise.

get_body_measurements

Retrieve body measurement history such as weight and body fat.

get_profile

Get user profile including training goals, methodology, and experience level.

get_training_summary

Get aggregate training statistics like total workouts and streaks.

get_training_volume

Get volume adaptation records per muscle group with fatigue and recovery data.

get_trainer_analysis

Get weekly AI trainer analysis logs with recommendations and insights.

get_weekly_schedule

Get the planned weekly training schedule.

get_workout_templates

Retrieve saved workout templates with exercise configurations.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational