GetFit MCP server
Which MCP servers are GetFit's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry nameapp.thegetfit/getfitverified in the MCP registry
The registry name sits under thegetfit.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools5
- Server calls itselfgetfit
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 117 ms.
- Its tools do none of the product's use cases we checked: See which athletes logged each day's session; Fork a public program and adapt it for your own athletes.
Once connected
- Parameters are untyped or undescribed in 4 of 5 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score69 of 100answers 100 · does the job 0 · definitions 87 · context 100 · connects 100
- What an agent can do with it0 of 2 use cases
- Answered100% of days11 of 11 daily checks
- Median first answer131 ms
- Space in an agent's context≈ 923 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsB · 87 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 4 of 5
What an agent can do with it
- not sure · Build multi-week strength programs from reusable workout blocks
- cannot · See which athletes logged each day's session
- cannot · Fork a public program and adapt it for your own athletes
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
build_workoutWhat workout can I do with this time, this gear, and this body? GetFit's coach builds a complete session that fits the minutes, uses only the equipment they have, and steers around anything they want to avoid. Give the person the whole…
search_workoutsWhat workouts are on GetFit for legs / 20 minutes / dumbbells? Searches published workouts on Explore by body area, name, exercise and gear. If nothing fits, say so and offer build_workout to make one. Inputs: query, focus, max_minutes…
get_workoutShow me that workout in full. Returns author, discipline, duration, warm-up, coach note and every exercise (sets, reps, rest, cues). Input: slug from search_workouts. Example: {"slug":"the-45-minute-pull-day"}.
list_contributorsWho posts workouts on GetFit? Lists people with published workouts: handle, name, bio, location, workout count. No inputs.
get_contributorWho is this GetFit contributor and what have they posted? Input: handle from list_contributors. Example: {"handle":"jenna"}.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"getfit": {
"type": "http",
"url": "https://thegetfit.app/mcp-server"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http thegetfit https://thegetfit.app/mcp-serverclaude.ai, ChatGPT and other clients: add https://thegetfit.app/mcp-server as a custom connector in the settings.
OpenAPI spec
3 paths, read 2026-10-25. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.