Skip to main content
Glama
vitaliemiron

Cookidoo MCP Server

by vitaliemiron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Cookidoo MCP Server

No user-submitted related servers found.

    Related Servers

    • cookidoo-mcp

      jsaedtler
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to upload and manage Thermomix recipes on Cookidoo, including structured steps with Thermomix settings, images, and access to shopping lists and meal planning.
      11
      MIT

    • cookidoo-mcp

      josepenam
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables to browse, compare, plan, and shop from Cookidoo, and save arbitrarily tweaked custom recipes back to your account.
      1
      MIT

    • cookidoo-mcp

      sisques-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Cookidoo, enabling AI tools to search recipes, manage shopping lists, and retrieve account and subscription information.
      2
      GPL 3.0

    • Tandoor MCP Server

      mc-mario
      A
      license
      B
      quality
      C
      maintenance
      Enables interaction with Tandoor recipe management system to create, manage, and search recipes, as well as create and auto-generate meal plans with automatic ingredient and keyword creation.
      11
      47 npm
      3
      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 16 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: recipe viewing (get_recipe_details vs get_custom_recipe_details are distinct by source), meal-plan operations are clearly separated into add/remove/move, and the custom-recipe workflow is well delineated. However, get_recipe_details and get_custom_recipe_details could cause some confusion, and update_custom_recipe_steps vs update_custom_recipe_ingredients require careful reading of descriptions to distinguish.

    Naming Consistency3/5

    There is a consistent verb-based pattern (get_, add_, remove_, move_, copy_, generate_, validate_, calculate_, update_, upload_, connect_to_). However, the naming mixes verbs with varying patterns: 'get_*' vs 'upload_custom_recipe' vs 'generate_recipe_structure' vs 'calculate_annotation_position' — the prefixes aren't uniformly 'get_' vs 'create_' vs 'update_'. The 'custom_recipe' vs 'recipe' noun ordering is also inconsistent (copy_recipe_to_custom vs get_custom_recipe_details).

    Tool Count4/5

    16 tools for a Cookidoo integration server is on the higher end but reasonable given the breadth of features covered: authentication, recipe retrieval, meal planning, custom recipe management, and image upload. Each tool serves a distinct purpose, though a few (calculate_annotation_position, validate_guided_recipe_structure) are niche and could arguably be consolidated.

    Completeness4/5

    The surface covers the major workflows: authentication, recipe lookup, meal planning (add/remove/move), and full custom-recipe lifecycle (structure generation, validation, upload, step/ingredient updates, image upload). Minor gaps include no tool to delete a custom recipe or delete a recipe from the meal plan entirely (only remove per-day), and no shopping-list add/modify operation besides retrieval.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources