aimharder-mcp

A local MCP server for querying AimHarder from clients that support Model Context Protocol. An independent project, neither affiliated with nor endorsed by AimHarder.

Status: account and gym discovery implemented (#2). Authentication and gym selection have been checked against a real account through an MCP client over stdio. Gym time zones remain unverified and are returned explicitly as unknown. Class schedules, workouts, bookings, and personal activity remain pending; the complete MVP is not delivered yet.

Install

Requirements: Node.js 24 LTS and pnpm 12.5.1. The supported Node major is recorded in .node-version; use your preferred Node version manager. Install pnpm with npm install --global pnpm@12.5.1 if necessary.

git clone https://github.com/rudeayelo/aimharder-mcp.git
cd aimharder-mcp
pnpm install --frozen-lockfile
pnpm typecheck
pnpm test
pnpm build

Run pnpm build after source updates. Dependencies are locked; the MSW browser-worker postinstall is disabled because this project uses Node tests only. There is no database, service deployment, or package publication step.

Related MCP server: garmin-mcp

Configure and connect

Credentials are supplied through the server process environment. A secrets manager is optional. You can inject variables with your preferred manager, configure them in your MCP client, or use a local environment file:

cp .env.example .env
chmod 600 .env

Edit .env locally to set the values. Keep it private; Git ignores it. The application does not automatically load environment files: Node's --env-file option in the example below loads it explicitly.

Configure a local stdio server in any MCP-compatible client. This common configuration format uses illustrative absolute paths; replace them with your Node 24 executable and checkout paths:

{
  "mcpServers": {
    "aimharder": {
      "command": "/absolute/path/to/node",
      "args": [
        "--env-file=/absolute/path/to/aimharder-mcp/.env",
        "/absolute/path/to/aimharder-mcp/dist/index.js"
      ]
    }
  }
}

If your client supplies the environment directly, omit --env-file. Use the Node executable directly so package-manager output cannot interfere with MCP stdout. pnpm start is also available for a shell with credentials already exported; the process waits for MCP messages on stdin. Authentication is lazy: initializing the connection and listing tools do not contact AimHarder.

Tool: get_account_context

Call with {} to select the only gym or configured default. Call with {"gymId":"another-verified-gym"} to select another discovered gym for that query without restarting. Subsequent omitted selections still use the default. Multiple gyms always require a valid configured default, including when using an override. A missing or inaccessible default returns an error with the discovered accessibleGymIds so you can configure one and restart.

Example response using anonymized data:

{
  "account": { "authenticated": true },
  "gyms": [
    { "id": "sample-gym", "name": "Gimnasio de prueba", "timeZone": null, "timeZoneStatus": "unverified" }
  ],
  "selectedGym": { "id": "sample-gym", "name": "Gimnasio de prueba", "timeZone": null, "timeZoneStatus": "unverified" },
  "notices": ["Gym time zones have not been verified. Do not infer gym-local dates from the computer time zone."]
}

The same result is available as MCP structured content and JSON text. Gym names preserve the source language and must be treated as untrusted data. Account identity is verified internally; personal names, account IDs, photos, permission hashes, credentials, and session tokens are not returned.

Gym IDs are the subdomain labels from verified account memberships, not an interpretation of AimHarder's numeric id or boid fields. Discovery is fetched on every query. Currently supported memberships have role: "client" and a centre_url hostname under .aimharder.es; other formats return a clear error rather than silently omitting gyms. No cross-domain .com authentication is attempted.

Session and errors

The API client is separate from MCP. Only the verified login POST and account discovery GET are enabled. Cookies stay in memory, redirects are rejected, each HTTP request times out after 15 seconds, and response bodies are limited to 1 MiB. Concurrent tool requests are serialized around the account session.

An empty identity result or query HTTP 401 permits one reauthentication and one retry of the query. Repeated expiration stops with SESSION_EXPIRED. HTTP 403/429 stops with ACCESS_RESTRICTED, without reauthentication. Malformed responses, transport failures, and identity mismatches are errors, never empty successful results. Login failures, including unsupported additional-authentication responses, stop further login attempts until the server restarts. Upstream messages are not echoed. Specific invalid-password, 2FA, and restriction payloads have not been verified live; see API research.

INVALID_CONFIGURATION requires correcting the environment. DEFAULT_GYM_REQUIRED and GYM_NOT_ACCESSIBLE require selecting a verified gym. UNSUPPORTED_MEMBERSHIP or INVALID_RESPONSE indicate a contract this version cannot establish safely. Do not infer a gym time zone from location, browser settings, or the computer's time zone.

Verification

Automated tests use the public MCP interface, real API client, and anonymized HTTP fixtures. They require no real account and reject unhandled network requests:

pnpm typecheck
pnpm test
pnpm build

For an explicitly authorized live read-only check with your own account:

AIMHARDER_LIVE_CHECK=1 node --env-file=.env scripts/live-check.mjs

With already injected credentials, AIMHARDER_LIVE_CHECK=1 pnpm test:live is equivalent. The harness launches the built server over stdio, checks authentication, default and explicit selection, and rejects an unverified gym. It prints only a sanitized summary. This performs real login and discovery requests, not bookings or profile changes. Validation results and limitations distinguish live observations from fixture coverage.

Remaining MVP

Class schedules and occupancy, published future workouts, upcoming bookings and history, and personal activity queries remain planned. The first combined experience will answer "What are we doing in tomorrow's WOD, and when am I booked?". Creating or canceling bookings, automation, per-exercise analysis, a UI, and a remote service remain outside the MVP.

Documentation

• Domain glossary.

• Scope, acceptance criteria, and implementation tickets.

• MVP specification.

• API research and validation gaps.

• Validation results.

• Implementation stack and session decision.

• MVP decision.

• API client separation.

• Credentials and read-only operations.

• Public repository and license.

• Agent instructions.

All project content is maintained in English.

License

MIT.