Skip to main content
Glama

Related Servers

Alternatives to wetaca-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude or any MCP client to manage WHMCS clients, services, orders, invoices, quotes, domains, tickets and system settings through the WHMCS External API, with 128 typed tools plus a generic caller for any of the 162 API actions. Includes read-only mode, confirmation prompts for destructive operations, and opt-in gating for sensitive actions.
      46 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to manage orders, stock, purchase orders, pickwaves, and channel listings in a user's own e-commerce account through 104 MCP tools, with dry-run defaults for writes.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to read a US HelloFresh meal-kit subscription, browse upcoming weeks and menus, and suggest meals for configurable planner profiles. It can also pick meals, adjust box size or delivery day, and skip weeks, with every change confirmation-gated and verified by re-reading HelloFresh.
      26
      1,041 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI agents and terminal users to manage Grocy household inventory, shopping lists, recipes, chores, and related household operations through MCP tools and a command-line interface.
      89
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to act as the memory and reasoning layer for nutrition tracking, letting users log meals from label photos or descriptions, save foods, recipes, meal-prep containers, and restaurant orders, record weigh-ins, and query targets, progress, and projections as tool calls. All writes are previewed with dry runs, checked for plausibility, and reversible.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an assistant to query and manage a Grocy household's stock, shopping lists, recipes, meal plans, chores, tasks, batteries, equipment and master data through 76 typed MCP tools, with writes off by default and opt-in once enabled. Supports safe, reversible changes such as booking receipts into stock, ticking off shopping items and undoing stock transactions.
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 37 tools

    Disambiguation4/5

    Each tool pairs a resource with a distinct action (orders_cancel vs orders_show, subscription_pause vs suggestion_pause vs profiles_pause) and the descriptions carefully spell out the scope differences, including the explicit warning that wetaca_vouchers_skip duplicates wetaca_suggestion_pause. The remaining confusion risk is concentrated in the three pause/resume families and dry-run-vs-confirm semantics, which are documented but still easy to misselect.

    Naming Consistency5/5

    Every tool follows wetaca_<resource>_<verb> snake_case (wetaca_orders_list, wetaca_suggestion_edit, wetaca_addresses_remove), with the only deviations being single-command mirrors like wetaca_me, wetaca_doctor and wetaca_usage that still read clearly. The pattern is predictable enough that an agent can guess a tool name from the domain.

    Tool Count3/5

    37 tools is heavy, but the surface mirrors a real CLI spanning orders, subscription, profiles, deliveries, menu, dishes, addresses, vouchers, gift cards, wallet, auth and config. A handful of peripheral entries (config_path, config_get, config_set, doctor, usage) add cognitive load without much agent value, pushing this above the comfortable 3-15 range.

    Completeness4/5

    Read plus lifecycle coverage is solid across every domain: orders list/show/cancel, subscription show/pause/resume, profiles list/pause/resume, suggestions show/edit/pause/resume, addresses list/save/remove, vouchers, gift cards, wallet. Notable gaps are the absence of address update (save always creates a new, non-idempotent record) and no profile creation or subscription (re)start, though agents can work around these.