
Fitaf Ai Fitaf Ai Mcp
FitAF AI MCP is a MCP server that lets agents manage FitAF workouts, nutrition, goals, progress, and wearable sync over Smithery.
About
The FitAF AI MCP server exposes the FitAF fitness platform to Claude Code, Cursor, Codex, and other MCP clients so a developer can treat training and nutrition data like any other integration. Instead of switching apps to adjust macros, check weekly volume, or review goal progress, you register the Smithery remote with your Smithery API key and let the agent call tools backed by FitAF. That pattern fits developers shipping health-adjacent products—coaching apps, habit trackers, or internal wellness tools—who need programmatic access without writing a custom REST layer first. It is a task-oriented MCP bridge, not a methodology skill: one primary job is connecting agent workflows to FitAF accounts, wearables, and synced metrics. Expect Bearer authentication on every request and a hosted streamable-http transport rather than a repo you clone and run locally.
- Manage workouts, nutrition, goals, and progress across FitAF from MCP tools
- Connect wearables and sync activity into one agent-accessible surface
- Streamable HTTP remote on Smithery with Bearer auth
- Version 1.0.0 server schema aligned with MCP 2025-09-29
- Smithery-hosted endpoint—no local server repo required to register
Fitaf Ai Fitaf Ai Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http fitaf-ai-fitaf-ai-mcp https://server.smithery.ai/@fitaf-ai/fitaf-ai-mcp/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
What it does
Let your coding agent log workouts, meals, goals, and wearable sync on FitAF without leaving the chat.
Who is it for?
Best when you're prototyping fitness, coaching, or habit products that should read and write FitAF data through an agent.
Skip if: Skip if you do not use FitAF or only need generic step-count APIs with no FitAF account.
What you get
After registration, your agent can query and update FitAF training and nutrition context inside the same coding session.
- Registered Smithery remote pointing at @fitaf-ai/fitaf-ai-mcp
- Agent-callable tools for workouts, nutrition, goals, and progress
- Wearable-connected sync path into agent workflows
By the numbers
- Server version 1.0.0 per MCP 2025-09-29 schema
- Single streamable-http remote on server.smithery.ai
- One required secret header: Authorization Bearer smithery_api_key
Recommended MCP Servers
How it compares
MCP integration to FitAF, not a local fitness skill or workout plan generator.
FAQ
Who is ai.smithery/fitaf-ai-fitaf-ai-mcp for?
Developers and agent users on FitAF who want wearable-backed workout and nutrition control from Claude Code, Cursor, or Codex.
When should I use ai.smithery/fitaf-ai-fitaf-ai-mcp?
Use it when you are building or operating tooling that must sync goals, logs, or wearable data with FitAF during the integrations phase.
How do I add ai.smithery/fitaf-ai-fitaf-ai-mcp to my agent?
Create a Smithery API key, add the streamable-http remote URL in your MCP config, and set Authorization to Bearer your Smithery key.