Fitaf Ai Fitaf Mcp
Expose FitAF body metrics, habits, SMART goals, and trends to your agent for coaching or app prototypes.
Overview
FitAF MCP is a Build-phase MCP server that tracks FitAF workouts, nutrition, body metrics, habits, SMART goals, and trends for agents via Smithery.
What is this MCP server?
- Track workouts, nutrition, body metrics, habits, and SMART goals via MCP
- Insights and trends surfaced for agent-driven summaries and planning
- Connect external sources through FitAF-backed tools (per catalog description)
- Smithery streamable-http remote with required Bearer authentication
- Distinct Smithery package @fitaf-ai/fitaf-mcp from the fitaf-ai-mcp variant
- Catalog version 1.0.0 on MCP schema 2025-09-29
- One streamable-http remote endpoint
- GitHub source not listed in server.json for this package
What problem does it solve?
Habit loops and SMART goals in FitAF are invisible to your agent unless you build or register an MCP bridge.
Who is it for?
Builders shipping habit or body-composition features that already standardize on FitAF and Smithery-hosted MCP.
Skip if: Users who only need the broader wearable-focused fitaf-ai-mcp variant or who are not on FitAF.
What do I get? / Deliverables
Your agent can read trends and update habits and goals on FitAF without custom REST glue in every project.
- Configured remote for server.smithery.ai/@fitaf-ai/fitaf-mcp/mcp
- Agent tools for workouts, nutrition, metrics, habits, and goals
- Trend and insight queries usable in build-time automation
Recommended MCP Servers
Journey fit
The server is a hosted bridge to FitAF APIs, which builders attach while wiring external services into their product. Habits, SMART goals, and body-metric tools are integration-layer capabilities rather than shipping or growth analytics alone.
How it compares
FitAF metrics-and-habits MCP remote, not an on-device training plan skill.
Common Questions / FAQ
Who is ai.smithery/fitaf-ai-fitaf-mcp for?
Solo builders and agent users who rely on FitAF for habits, SMART goals, and body metrics and want MCP access from their IDE.
When should I use ai.smithery/fitaf-ai-fitaf-mcp?
Use it when integrating trend insights, habit tracking, or goal updates into an agent workflow during backend or agent-tooling setup.
How do I add ai.smithery/fitaf-ai-fitaf-mcp to my agent?
Add the @fitaf-ai/fitaf-mcp Smithery remote to MCP settings and supply Bearer {smithery_api_key} on the Authorization header.