ckd-meal-plan-mcp
Related Servers
Alternatives to ckd-meal-plan-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD nutrition and food calculations, enabling energy/protein targets, food nutrient lookup, substitutions, meal summaries, and drug-nutrient interaction checks.8-
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD follow-up management, providing tools to schedule follow-ups based on KDIGO 2024 guidelines, retrieve follow-up records, compute adherence scores, and access PEW history.4-
- FlicenseAqualityBmaintenanceGenerates multi-day CKD meal plans for children based on PRNT targets (energy, protein, potassium, phosphorus, sodium), providing nutrient summaries and target achievement rates for dietitians.2-
- FlicenseAqualityBmaintenanceRead-only MCP server providing pediatric CKD patient master data with tools for patient profiles, diagnosis, nutrition ceilings, guardian verification, and patient lists, designed for the CKDNutri project.5-
- AlicenseAqualityCmaintenanceProvides deterministic parental guidance for children with chronic kidney disease, including food safety checks, lab report interpretation, and nutrient-aware food substitutions based on authoritative guidelines and the Chinese Food Composition Table.12MIT
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD clinical calculations, providing eGFR-Schwartz estimation and KDIGO 2024 CKD staging, restricted to doctors.2-
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes: fetching diary data, analyzing it, generating plans, and managing food data are well separated. However, generate_meal_plan already writes to SQLite while save_meal_plan also writes the same generated plan, creating potential ambiguity about when to use each.
The vast majority of tools follow a consistent verb_noun pattern (e.g., get_patient_profile, search_food, list_meal_plans). The lone exception is knowledge_card, which is a noun without a verb, breaking the pattern slightly.
With 13 tools, the set is well-scoped for a specialized CKD meal-planning domain. Each tool addresses a specific need from patient data retrieval to meal plan generation and food lookup, without excessive fragmentation or bloat.
The server covers the core workflow: patient profiles, lab values, diary analysis, nutrition targets, meal plan generation/saving/listing, and food database queries. Minor gaps include lack of a tool to retrieve the full details of a saved meal plan (list only gives summaries) and no update/delete operations for plans.