Skip to main content
Glama
counterbeing

mealie-mcp-ts

by counterbeing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mealie-mcp-ts

No user-submitted related servers found.

    Related Servers

    • Mealie MCP Server

      mdlopresti
      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

    • Better Mealie MCP

      djwmarcx
      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.
      264
      18
      MIT

    • mealie-mcp

      retr083
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to search, import, create, update, and delete recipes, manage shopping lists and items, and plan meals by date through the Mealie API. Runs as a remote streamable-HTTP connector with built-in OAuth 2.1, so it can be added directly in Claude's mobile, web, or desktop apps without a third-party auth service.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target distinct resources and actions clearly, with recipe CRUD, meal plans, shopping lists, foods, categories, tags, and user info separated. The three recipe creation methods (manual, URL, HTML) share intent but are differentiated by input source, and test_scrape_url adds a validation step. Shopping list item operations are distinct from adding a whole recipe's ingredients.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern (list_, get_, create_, delete_, update_, upload_, add_, test_, parse_). Even longer names like create_recipe_from_url or get_todays_meal_plan follow the verb-first convention. There are no camelCase or mixed naming styles.

    Tool Count4/5

    27 tools is above the typical 'heavy' threshold, but the server covers many subdomains: recipes, meal plans, foods, shopping lists, categories, tags, user info, and URL scraping. Each tool has a defined role, though having three recipe creation variants inflates the count; a slightly leaner set could be achieved without losing functionality.

    Completeness3/5

    Core recipe management (CRUD plus image upload), meal plan basics, shopping list item operations, and URL scraping are well covered. However, there are notable gaps: no create_shopping_list or delete_shopping_list, no update/delete for categories or tags, no delete_food, and no update_meal_plan. These missing lifecycle operations could force users to rely on external tools or workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources