MyoAmigo exposes an MCP server so an AI agent can read your training history, log sets, and build plans on your behalf. There are 34 tools across history, logging, routines, plans, and analytics — /tools.json is the full catalog with input schemas.
You need a MyoAmigo account first — create one if you haven't. On first connect you'll be sent here to sign in and approve access; the agent never sees your password.
Once you've created a passkey — in the MyoAmigo app or on the sign-in page — that browser sign-in step is a single tap, no password.
https://api.myoamigo.com/mcpclaude mcp add --transport http myoamigo https://api.myoamigo.com/mcp
The first tool call opens the browser to sign in and approve access.
The server is a standard OAuth 2.1 protected resource. A compliant client discovers and connects on its own:
https://api.myoamigo.com/.well-known/oauth-protected-resource/mcphttps://api.myoamigo.com/api/auth/oauth2/registerS256); send resource=https://api.myoamigo.com/mcp so the
access token is audience-bound to this server.https://api.myoamigo.com/mcp (stateless JSON-RPC over HTTP POST).Use OAuth when your MCP client supports it. For scripts, CLIs, and agents that can't run a browser OAuth flow, your account can hold one personal API key. It authorizes the same 34 tools at the same endpoint — any HTTP client works:
curl -X POST https://api.myoamigo.com/mcp \
-H "Authorization: Bearer myo_sk_..." \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The key is shown once at creation — store it somewhere safe. Creating a new key replaces the old one immediately, and key requests are rate-limited per account. Treat it like a password: it can read and write your training data.
Checking your account…
/llms.txt · /tools.json · Home