Skip to main content
Glama
ai-mcp-garage

MyFitnessPal MCP Server

README.md
# mcp-myfitnesspal

TDQS

B3.1/5.0

Scored across 6 tools

Disambiguation3/5

The tools have clear distinctions in their data focus (exercise, macros, meals, summary, date range, water), but there is significant functional overlap between get_daily_summary and the more specific tools like get_daily_macros or get_daily_meals, which could lead to confusion about which to use for certain queries. The descriptions help clarify, but the boundaries are not perfectly distinct.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by descriptive nouns (e.g., get_daily_exercise, get_daily_macros). This uniformity makes the tool set predictable and easy to understand at a glance.

Tool Count4/5

With 6 tools, the count is reasonable for a fitness tracking domain, covering key aspects like daily data, summaries, and date ranges. It's slightly lean but well-scoped, though it might benefit from additional tools for actions like logging or updating data.

Completeness2/5

The tool set is severely incomplete as it only provides read-only operations (all 'get_' tools) with no ability to create, update, or delete data. For a fitness app like MyFitnessPal, this misses essential CRUD functionality such as logging meals, exercises, or water intake, which are core to the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues