Skip to main content
Glama
zachsnow

parsley-mcp

by zachsnow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to parsley-mcp

No user-submitted related servers found.

    Related Servers

    • Ordio MCP

      Abhilashachar
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Ordio restaurant operations platform, enabling AI assistants to manage inventory, orders, recipes, team, shifts, and reports.
      1
      -

    • cookwith-mcp

      valetdotdev
      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
      8 npm
      MIT

    • recipe-mcp

      valetdotdev
      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
      33 npm
      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.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, and the list-vs-search pairs (list_menus/search_menus, list_ingredients/search_ingredients, list_menu_items/search_menu_items) are clearly differentiated by their descriptions. The only mild overlap is between get_menu, get_menu_item, and get_recipe, but these map to genuinely different entities so an agent can select correctly.

    Naming Consistency5/5

    Every tool follows a clean snake_case verb_noun pattern (list_/search_/get_/clear_/configure_). The verbs are used consistently: list_* for enumeration, search_* for fuzzy query, get_* for single-entity fetch, matching the description semantics.

    Tool Count4/5

    19 tools is at the higher end but justified given the domain spans menus, recipes, ingredients, menu items, events, plus utility/auth tools (configure_token, clear_cache, get_access_token). Nothing feels redundant given the list/search/detail triad per entity.

    Completeness4/5

    The surface covers read operations comprehensively across all entities (list, search, get for menus/ingredients/menu items, plus recipes, events, stations, chef tags/users, report). There are no write/update/delete operations, but the server appears intentionally read-only (24h GET cache), and only minor detail getters (e.g. serving station, chef user) are absent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources