mcpbeat Sign in

Athlete Diary MCP Server

by athletediary Your server? Claim it
answering

Athlete Diary is answering right now. Last checked 11 min ago.

Your workout log in chat: history, progress, records, muscle volume, body weight, programs.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
166 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Athlete Diary every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add athlete-diary --transport http https://athletediary.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://athletediary.app/mcp
~/.codex/config.toml
[mcp_servers.athlete-diary]
url = "https://athletediary.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "athlete-diary": {
      "url": "https://athletediary.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "athlete-diary": {
      "type": "http",
      "url": "https://athletediary.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://athletediary.app/mcp streamable-http sign-in 157 ms 11 min ago

Alternatives to Athlete Diary

same job, measured the same way
RIRLift
by rirlift

Your RIRLift strength training log: workouts, progress, volume, recovery and program drafts.

answering
Roleora
by roleora

Log, search and summarise your work history in Roleora, the career record for professionals.

answering
Reps
by repsworkout

Your Reps gym log in Claude or ChatGPT: workouts, PRs, progress, routines and training plans.

answering
JustGains
by justgains

Save workouts, read training history and progress, search exercises, and log food in JustGains.

answering
Anatome
by anatome

Log workouts and meals by telling your AI. 873 exercises, muscle diagrams, food lookup.

36 tools answering
PumpX
by pumpx

Read-only access to your PumpX workout log: sessions, lift history, PRs, routines, measurements.

answering
DogNote
by rrebase

Read pet activity and weight history, and log events with your permission.

answering
Sport MCP
by sport-mcp

Strength-training log for iPhone: read workouts, records and progress; plan and log training.

answering

Athlete Diary — questions

Answers built from our own checks of this server.

Why is there no tool list for Athlete Diary?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Athlete Diary working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 166 ms. The bar chart above shows every period we have measured.
How do I connect Athlete Diary?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Athlete Diary?
No API key is involved. Athlete Diary answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Athlete Diary?
It answers our handshake in 166 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.