Use your training data inside Claude

Prerequisites

• A GymLogic account with at least one logged workout
• Claude Desktop installed (latest version recommended)

Setup

Two steps:

1. Add the Custom Connector — wire Claude Desktop to the GymLogic MCP server (~30 seconds).
2. Load the GymLogic Skill (recommended) — teach Claude how to use the tools well (~30 seconds).

If you can’t use OAuth or need a headless setup, see Alternative authentication below — Step 1 has a PAT / mcp-remote variant; Step 2 still applies.

Step 1 — Add the Custom Connector

1. Open Claude Desktop and go to Settings → Connectors.

2. In the Add custom connector dialog, fill in:

   • Name: Gymlogic
   • URL: https://mcp.gymlogic.me/functions/v1/mcp
   • Leave OAuth Client ID and OAuth Client Secret empty — GymLogic uses dynamic registration.

   Click Add.

3. Your browser opens to the GymLogic consent page. Sign in if prompted, then click Authorize.

4. Return to Claude Desktop. The connector now appears in your Connectors list.

Step 2 — Load the GymLogic Skill (recommended)

The connector exposes the tools; the Skill teaches Claude how to use them well — when to invoke each, the propose-confirm-act handshake required on every write, the per-side weight convention for unilateral equipment (#263), and bilingual French/English routing. Without it, Claude can still call the tools, but expect rougher edges (especially on writes and on coaching prompts that cross multiple tools).

1. Download the skill file from the repo: skills/gymlogic-mcp/SKILL.md. Use GitHub’s “Download raw file” button (top-right of the file viewer).

2. In Claude Desktop, open Customize → Skills, click the + icon next to “Skills”, and upload the SKILL.md file.

3. Make sure the skill toggle is on (top-right of the skill detail panel).

You’re set. The skill triggers automatically on training-related prompts (FR or EN) — no need to invoke it explicitly. The capabilities ask is a good first prompt: Claude will surface the full menu of what GymLogic can do.

Alternative authentication

For headless setups or Claude Desktop builds where the native Custom Connector UI isn’t available, replace Step 1 with one of the alternatives below. Step 2 (the Skill) still applies either way.

Personal Access Token (PAT)

If you want longer-lived auth or a headless setup, use a Personal Access Token instead of OAuth. Create one at gymlogic.me/account/api-tokens → — pick a lifetime, copy the glp_… value (shown once), and use the config below.

The cleanest PAT path on Claude Desktop is via the mcp-remote adapter (since the native UI doesn’t always expose a headers field for SSE servers). Heads up — the adapter has a few sharp edges:

{
  "mcpServers": {
    "gymlogic": {
      "command": "/Users/you/.nvm/versions/node/v20.9.0/bin/npx",
      "args": [
        "mcp-remote",
        "https://mcp.gymlogic.me/functions/v1/mcp",
        "--header",
        "Authorization: Bearer <YOUR_PAT>"
      ]
    }
  }
}

Config file with mcp-remote (no UI)

For Claude Desktop builds where the native Custom Connector UI isn’t available, or for headless setups, configure mcp-remote directly in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Same Node 18+ requirement and absolute-path recommendation as above.

{
  "mcpServers": {
    "gymlogic": {
      "command": "/Users/you/.nvm/versions/node/v20.9.0/bin/npx",
      "args": [
        "mcp-remote",
        "https://mcp.gymlogic.me/functions/v1/mcp"
      ]
    }
  }
}

Available tools

Nine tools — seven reads, two writes. Claude picks the right one based on what you ask.

Example conversation

A good first prompt is the one shown in the hero above — “what cool things can I do with the gymlogic connector?” — Claude surfaces the full menu of capabilities. From there, drill into specifics:

1. “What did I train this week?” — pulls your recent sessions
2. “How’s my push/pull balance over the last month?” — analyzes volume distribution
3. “What’s programmed for tomorrow?” — checks your active program
4. “Tell me about the Romanian Deadlift” — searches and fetches exercise details
5. “Based on all this, what should I focus on next?” — Claude reasons across all the data
6. “Propose a revised 4-day split from that — show me a create_program dry run, then apply if I confirm” — end-to-end adapt + save (replaces the current active program when applied)

Troubleshooting