Skip to main content
Glama

Related Servers

Alternatives to How-To-Cook

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      MCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.
      5
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for AI-powered recipe generation and transformation, enabling users to create custom recipes from natural language descriptions and modify existing ones to meet dietary and nutritional goals.
      2
      29 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI-powered recipe generation and transformation using natural language, supporting dietary restrictions, allergies, and nutritional goals.
      2
      5 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that transforms AI assistants into personal chefs by providing recipe recommendations and meal planning features based on the HowToCook repository.
      5
      3,486 npm
      773
      ISC
    • F
      license
      A
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage a recipe catalog, including listing, searching, adding, removing, and suggesting recipes, with optional Trello or local JSON storage.
      5
      -

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getAllRecipes retrieves all recipes, getRecipeById fetches a specific recipe by ID/name, getRecipesByCategory filters by category, recommendMeals creates personalized meal plans, and whatToEeat offers quick dish recommendations. There is no overlap or ambiguity in their functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with the prefix 'mcp_howtocook_' and use camelCase (e.g., getAllRecipes, getRecipeById). The naming is uniform and predictable across all tools.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a cooking/recipe domain. Each tool serves a distinct and essential function, from basic retrieval to advanced planning, making the count appropriate and efficient.

    Completeness4/5

    The toolset covers core operations like retrieval, filtering, and recommendation, but lacks CRUD capabilities for creating, updating, or deleting recipes. This is a minor gap, as agents can still perform most common tasks, but full lifecycle management is not supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues