Health · Remote MCP server
Fitness Tools
Deterministic fitness calculators — TDEE, adaptive TDEE, body fat, 1RM, macros — with consensus.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.almostjacked/fitness-tools- Version
- 0.3.4
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-24
- Updated
- 2026-07-24
- Publisher
- almostjacked (GitHub) · 3 servers with pages here
- Repository
- github.com/almostjacked/fitness-tools
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://fitness-tools-mcp.ajwallacemusic.workers.dev/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @almostjacked/fitness-tools-mcp | 0.3.4 | stdio |
How to connect Fitness Tools
Fitness Tools is a remote MCP server: there is nothing to install. Its endpoint is https://fitness-tools-mcp.ajwallacemusic.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @almostjacked/fitness-tools-mcp version 0.3.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @almostjacked/fitness-tools-mcp@0.3.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"fitness-tools": {
"command": "npx",
"args": [
"-y",
"@almostjacked/fitness-tools-mcp@0.3.4"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from almostjacked (GitHub)
| Server | Runs |
|---|---|
| Health Data (your own Supabase)Your health data (weight, macros, weigh-ins) as MCP tools — in your own Supabase, zero custody. | Local · stdio |
| Hevy (unofficial)Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key. | Remote & Local · HTTP, stdio |
More health servers
| Server | Runs |
|---|---|
| FitbitmcpPrivacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents. | Local · stdio |
| Fitfly EngineDeterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation. | Remote · HTTP |
| Fitness AI ConnectorGarmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing. | Remote · HTTP |
| Fitness InfluencerAI-powered fitness content creator tools: video editing, image generation, workout plans, analytics. | Local · stdio |
| FlareSignal IntelligenceFlare and Songbird intelligence with provenance, source health, MCP access and x402 readiness. | Remote · HTTP |
| fmcg.networkUSDA FoodData Central nutrient lookup, FDA recall watch, EU FMCG labelling via remote MCP. | Remote · HTTP |
| Fodda Brand IntelligenceBrand health & trend footprint across PSFK expert graphs with citable sources, not web summaries. | Remote · HTTP |
| Folklore Clinical Variant Interpretation MCPBioinformatics MCP for genomic variant interpretation, gene-disease evidence and literature. | Remote · HTTP |