fitfly-engine
Server Details
Deterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.8/5 across 10 of 10 tools scored. Lowest: 3.2/5.
Each tool has a clearly distinct purpose: changelog explains coaching decisions, get_program provides the full program, get_todays_session shows the immediate workout, list_swap_options and swap_exercise handle exercise substitution, log_workout records lifts, meal_plan and nutrition_targets cover nutrition, readiness_checkin handles daily readiness, and regenerate_program rebuilds the program. There is no ambiguity or overlap.
Most tools follow a verb_noun pattern (get_program, list_swap_options, log_workout, regenerate_program, swap_exercise). Two tools (changelog, meal_plan, nutrition_targets) are noun-only, which is a minor inconsistency but does not cause confusion. Overall, the naming is clear and predictable.
With 10 tools covering program viewing, daily sessions, exercise swapping, workout logging, nutrition, readiness, and program regeneration, the count is well-scoped for a fitness coaching engine. Each tool serves a clear need without redundancy.
The tool set covers core workflows: program management, workout execution, exercise swapping, nutrition, and readiness. However, there is no tool to update athlete profile data (e.g., body stats, goals), which is needed for regeneration based on profile changes. This is a notable gap that could cause agent failures.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!