Skip to main content
Glama
alex-zwingli

plan-to-eat-mcp

by alex-zwingli

Related Servers

Alternatives to plan-to-eat-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search recipes, compose nutritionally balanced meals, optimize weekly meal plans based on macro targets for family members, and generate consolidated grocery lists from a personal recipe database.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage recipes, meal plans, and shopping lists in Mealie through natural language, supporting CRUD operations and URL-based recipe imports.
      27
      935 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Mealie for recipe management, meal planning, and shopping list operations. Supports searching and managing recipes, creating meal plans, and generating shopping lists from recipes or meal plans.
      7
      MIT
    • A
      license
      D
      quality
      B
      maintenance
      Provides complete access to Mealie's API for managing recipes, meal plans, shopping lists, households, and more via natural language from AI assistants.
      266
      19
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with AnyList for managing shopping lists, recipes, and meal planning. Users can retrieve recipe details, add ingredients to lists, and schedule meals on their AnyList calendar.
      10
      -

    TDQS

    B3.3/5.0

    Scored across 36 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but there is real overlap between duplicate_planner_event and add_leftover_meal (both can mark a duplicate as a leftover). list_planner_events and get_planner_week also cover similar ground, and delete_frozen_recipe is really a 'mark consumed' action, not a delete, which could mislead an agent.

    Naming Consistency4/5

    Tool names mostly follow a clear verb_noun pattern like add_planner_recipe, delete_recipe, list_stores. Minor inconsistencies exist: list_ vs get_ for overlapping reads, set_planner_servings vs update_planner_*, and delete_frozen_recipe for a non-delete operation, but overall the naming is predictable.

    Tool Count2/5

    36 tools is a lot for an MCP server, especially with many simple taxonomy listers (list_cuisines, list_courses, list_tags, etc.). The broad domain justifies some of the count, but it feels heavy and could be consolidated or scoped down.

    Completeness4/5

    The core domains are well covered: recipes have full CRUD, planner events support create/read/update/delete/move/reorder, and the shopping list has add/update/remove/restore. Minor gaps exist: menus and friends are list-only, and there is no direct way to view a single planner event or permanently delete shopping list lines.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues