Garmin MCP Server

This Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible clients.

Features

• List recent activities

• Get detailed activity information

• Access health metrics (steps, heart rate, sleep)

• View body composition data

Related MCP server: Garmin Connect MCP Server

Setup

Local Development

1. Install the required packages on a new environment:

uv sync

Remote Deployment (Railway)

Want to host this MCP server remotely and access it from AI assistants like Poke? See:

• SETUP_GUIDE.md - Quick start guide

• RAILWAY_DEPLOYMENT.md - Detailed deployment instructions

• Quick deploy: Run ./deploy_to_railway.sh (requires Railway CLI)

Running the Server

Configuration

Your Garmin Connect credentials are read from environment variables:

• GARMIN_EMAIL: Your Garmin Connect email address

• GARMIN_EMAIL_FILE: Path to a file containing your Garmin Connect email address

• GARMIN_PASSWORD: Your Garmin Connect password

• GARMIN_PASSWORD_FILE: Path to a file containing your Garmin Connect password

File-based secrets are useful in certain environments, such as inside a Docker container. Note that you cannot set both GARMIN_EMAIL and GARMIN_EMAIL_FILE, similarly you cannot set both GARMIN_PASSWORD and GARMIN_PASSWORD_FILE.

With Claude Desktop

1. Create a configuration in Claude Desktop:

Edit your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server configuration:

{
  "mcpServers": {
    "garmin": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "--from",
        "git+https://github.com/Taxuspt/garmin_mcp",
        "garmin-mcp"
      ],
      "env": {
        "GARMIN_EMAIL": "YOUR_GARMIN_EMAIL",
        "GARMIN_PASSWORD": "YOUR_GARMIN_PASSWORD"
      }
    }
  }
}

Replace the path with the absolute path to your server file.

2. Restart Claude Desktop

With MCP Inspector

For testing, you can use the MCP Inspector from the project root:

npx @modelcontextprotocol/inspector uv run garmin-mcp

Usage Examples

Once connected in Claude, you can ask questions like:

• "Show me my recent activities"

• "What was my sleep like last night?"

• "How many steps did I take yesterday?"

• "Show me the details of my latest run"

Security Note

Troubleshooting

If you encounter login issues:

1. Verify your credentials are correct

2. Check if Garmin Connect requires additional verification

3. Ensure the garminconnect package is up to date

For other issues, check the Claude Desktop logs at:

• macOS: ~/Library/Logs/Claude/mcp-server-garmin.log

• Windows: %APPDATA%\Claude\logs\mcp-server-garmin.log

Garming Connect one-time code

If you have one-time codes enabled in your account, you need to login at the command line first to set the token in the interactive cli.

The app expects either the env var GARMIN_EMAIL or GARMIN_EMAIL_FILE. You can store these in files with the following command.

echo "your_email@example.com" > ~/.garmin_email
echo "your_password" > ~/.garmin_password
chmod 600 ~/.garmin_email ~/.garmin_password

Then you can manually run the login script.

GARMIN_EMAIL_FILE=~/.garmin_email GARMIN_PASSWORD_FILE=~/.garmin_password uvx --python 3.12 --from git+https://github.com/Taxuspt/garmin_mcp garmin-mcp

You will likely see

Garmin Connect MFA required. Please check your email/phone for the code.
Enter MFA code: XXXXXX
Oauth tokens stored in '~/.garminconnect' directory for future use. (first method)

Oauth tokens encoded as base64 string and saved to '~/.garminconnect_base64' file for future use. (second method)

After setting the token at the cli, you can use the following in Claude, without the env vars because the Oauth tokens have been set.

"garmin": {
  "command": "uvx",
  "args": [
    "--python",
    "3.12",
    "--from",
    "git+https://github.com/Taxuspt/garmin_mcp",
    "garmin-mcp"
  ]
}