Skip to main content
Glama
xiaobenyang-com

cook-tool

by xiaobenyang-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to cook-tool

No user-submitted related servers found.

    Related Servers

    • Recettes MCP Server

      Symfomany
      F
      license
      C
      quality
      D
      maintenance
      Enables management of culinary recipes through web scraping from sites like Marmiton.org, recipe generation, ingredient management, and querying a MongoDB database of recipes, comments, users, and utensils.
      18
      -

    • How-To-Cook

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      An AI recipe recommendation server based on the MCP protocol, providing functions such as recipe query, classification filtering, intelligent dietary planning, and daily menu recommendation.
      5
      1
      Apache 2.0

    • HowToCook-MCP Server

      kureha4
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to recommend recipes, plan weekly meals, and solve the "what to eat today" problem by providing access to a comprehensive Chinese recipe database with smart filtering by categories, allergies, and dietary restrictions.
      5
      2,761 npm
      ISC

    • foodmcp

      carleshub
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for cooking and recipe management powered by Spoonacular API. Enables natural-language recipe search, ingredient-based discovery, nutrition breakdowns, and ingredient substitutions.
      -

    • Recipe By Api Ninjas MCP

      BACH-AI-Tools
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables users to search for recipes and cooking instructions via the API Ninjas Recipe API. It supports querying specific dishes and provides paginated results for recipe discovery.
      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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_all_dishes retrieves a list of dish names (menu), while get_dish_content fetches detailed content for a specific dish based on its name. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming (get_all_dishes, get_dish_content). The naming is predictable and readable throughout.

    Tool Count2/5

    With only 2 tools, the server feels thin for a cooking/recipe domain. It lacks essential operations like creating, updating, or deleting dishes, which limits its utility and scope. A minimal CRUD set would typically have at least 3-4 tools.

    Completeness2/5

    The tool surface is severely incomplete for a cooking domain. It only provides read operations (get all and get details), missing create, update, delete, search, or other lifecycle management tools. This will likely cause agent failures when trying to perform full workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources