Calorie Tracker MCP
Related Servers
Alternatives to Calorie Tracker MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA filesystem-based MCP server that turns any MCP-capable AI agent into a conversational calorie and protein tracker with natural-language estimates, confidence-aware logging, daily/weekly progress, food-history search, and export, working offline with local fallback data.15 npmMIT
- FlicenseNot gradedqualityBmaintenanceLocal-first nutrition tracker MCP server for Hermes, enabling food, alias, recipe, and meal log management with SQLite persistence.-
- AlicenseNot gradedqualityDmaintenanceEnables users to track daily calorie consumption by logging meals through natural language and searching a comprehensive food database. It provides daily summaries, weekly reports, and persistent SQLite storage to monitor dietary trends and goals.15 npmMIT
- FlicenseNot gradedqualityCmaintenanceOffline MCP server for logging workouts, tracking dietary macros, and retrieving daily summaries, all stored in local SQLite. Enables fitness tracking via natural language in MCP-compatible clients.-
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that stores nutrition, biomarker, and wearable data in SQLite and exposes it as Model Context Protocol tools, enabling MCP-aware agents to log meals, query trends, and run correlations.1MIT
- FlicenseBqualityDmaintenanceA personal fitness tracking server that enables logging and querying workouts, nutrition, and body metrics through a local SQLite database. Integrates with OpenNutrition MCP for food logging and supports exercise history tracking for workout progression.17-
TDQS
Scored across 11 tools
Each tool targets a distinct operation on meals, goals, or summaries. get_meal/get_meal_history/list_meals are differentiated by single-item, revision-history, and filtered-list purposes. Update/delete/restore are clearly distinct state-transition actions with unique semantics.
All tools follow a consistent verb_noun snake_case pattern (get_, set_, list_, log_, update_, delete_, restore_, export_, log_). Verbs are apt and descriptive, and the pattern is uniform throughout with no stylistic mixing.
Eleven tools is well within the ideal 3-15 range for a calorie tracker domain. Each tool earns its place: core CRUD (log/get/list/update/delete/restore), goals management, history, summary reporting, and export capabilities. No redundancy or bloat.
The surface covers the full meal lifecycle (log, read, list, update, delete, restore), goals get/set, history, summary, and export—a thorough set. Minor gaps exist, such as no bulk-delete or goal-archival/cleanup operations, but agents can accomplish all core workflows without dead ends.