Connection surface

Connect Meridian To Claude

This is the tiny operational layer for the rewrite. It shows which athlete roots exist, which local sources are ready, and which OAuth endpoints Claude or other MCP clients should use.

Shell Session

No active shell session.

Sign in with Google

Athlete Roots

Marcus Wendt 68b779bc-3744-4385-8ae2-3e992ed1c29c 48ed952b-4e8b-4f41-9ce7-eceb74f705b6 Eric

Local Source Readiness

Local filesystem bootstrap now lives in the CLI only. The hosted Crystalline shell focuses on auth, connected sync, and MCP access.

  • Strava · missing
    CLI-only: local Strava filesystem import
  • WHOOP · missing
    CLI-only: local WHOOP filesystem import
  • Weight log · missing
    CLI-only: local weight log import

MCP Setup

  • Authorization endpoint: https://meridian.coach/api/oauth/authorize
  • Token endpoint: https://meridian.coach/api/oauth/token
  • Client registration: https://meridian.coach/api/oauth/register
  • Protected resource: https://meridian.coach/api/mcp

Connected Sync

Use stored OAuth credentials to fetch fresh Strava, WHOOP, and Withings data into the athlete-scoped Crystalline cache, then import that data straight into the pure-memory store.

Sign in with Google before running connected syncs.

Signed-In Connection State

Sign in to inspect athlete-scoped connection state and run bootstrap syncs.

Bootstrap Sync

Local filesystem bootstrap now lives in the CLI only. The hosted Crystalline shell focuses on auth, connected sync, and MCP access.

For local filesystem imports, use the CLI and then return here for connected-service syncs and MCP auth.

pnpm meridian sync_data --help

Current Product Direction

  • Use Claude as the primary coaching surface.
  • Keep this web app for auth, consent, integrations, and status only.
  • Keep durable state in athletes, evidence, theses, actions, and races.