Skip to main content
Glama
Rubio-Enterprises

grocy-mcp

by Rubio-Enterprises
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to grocy-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Grocy API

      saya6k
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables interaction with Grocy's API through MCP, allowing management of grocery inventory, shopping lists, and household tasks via natural language.
      119 npm
      29
      MIT

    • grocy-mcp

      rusty4444
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage household operations including groceries, inventory, chores, recipes, and shopping lists through the Grocy self-hosted ERP system.
      3
      MIT

    • mise-mcp

      LinusU
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients like ChatGPT and Claude to manage a household's shared food inventory, meal plans, recipes, and preferences through natural language, with atomic updates and audit logging.
      -

    • grocy-mcp

      anishanilkumar
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Grocy that enables AI assistants to read and manage pantry stock, product catalogs, and shopping lists, with safety checks against common errors.
      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

    C2.9/5.0

    Scored across 89 tools

    Disambiguation4/5

    Most tools have distinct scopes with clear descriptions and cross-references (e.g., stock_search vs stock_barcode_lookup). Some overlap exists between recipe_fulfillment and recipe_consume_preview, and between shopping_list_set_amount and shopping_list_update, but descriptions help disambiguate. Overall, an agent can generally tell tools apart despite the large set.

    Naming Consistency4/5

    The dominant pattern is <domain>_<action>_tool, which is predictable and readable. However, singular/plural prefixes are inconsistent (chores_list vs chore_execute, batteries_list vs battery_details), and a few tools like discover_candidates_tool break the pattern. Still, the convention is mostly consistent.

    Tool Count2/5

    89 tools is far above the typical well-scoped range and feels excessive. Many tools are near-duplicates (six print label tools, multiple shopping-list population tools, and generic entity CRUD alongside domain-specific CRUD). This could be consolidated with parameterized tools, making the surface heavy and harder to navigate.

    Completeness3/5

    Core workflows (stock, shopping list, recipes, chores, tasks, meal plans, batteries, equipment) are well covered. However, there are notable lifecycle gaps: recipe deletion, chore update, location update/delete, battery delete, equipment delete, and file listing are missing. Generic entity tools partially mask these gaps but require low-level knowledge, so agents may hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources