Skip to main content
Glama
YawLabs

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yawlabs/lemonsqueezy-mcp

No user-submitted related servers found.

    Related Servers

    • lemonsqueezy-mcp

      heysash
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language interaction with Lemon Squeezy accounts via MCP tools for managing subscriptions, orders, discounts, license keys, and more, with built-in security and audit logging.
      69 npm
      MIT

    • mcp-server-woocommerce

      AmitGurbani
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.
      100
      98 npm
      2
      MIT

    • invoiceninja-mcp

      ambaloo
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.
      32
      20 npm
      2
      MIT

    • Recharge Storefront API MCP

      bearded-giant
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server that provides complete access to the Recharge Storefront API endpoints. Enables AI assistants to manage subscriptions, customers, orders, and billing through a standardized interface.
      2
      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

    A3.7/5.0

    Scored across 64 tools

    Disambiguation4/5

    Most tools target distinct resources with clear get/list/create/update/delete boundaries. The only notable overlap is ls_archive_customer vs. ls_update_customer's status field, but the descriptions explicitly call this out home. Sink and license tools are clearly separated.

    Naming Consistency5/5

    All tools follow the pattern ls_verb_noun consistently, using standard verbs like get_, list_, create_, update_, delete_. The only slight deviations are the two sink tools (ls_sink_events_list, ls_sink_event_mark_processed), but they still retain the prefix and a clear verb-noun structure.

    Tool Count2/5

    With 64 tools, this server is far beyond the recommended 3-15 range and crosses the 50+ threshold for extreme mismatch. While the scope justifies many resources, the sheer volume imposes significant cognitive load on agents and makes tool selection error-prone.

    Completeness3/5

    The surface covers most lifecycle operations for orders, subscriptions, customers, discounts, license keys, and webhooksherches, but product and variant creation/update are missing, forcing agents to rely on external means for catalog management. This is a notable gap for a full commerce server.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources