Skip to main content
Glama

Related Servers

Alternatives to Lemon Squeezy Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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.
      24 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants such as Claude, ChatGPT and Cursor to manage an open-source subscription backend: setting up products, entitlements, offerings and packages, looking up customers, granting or revoking access, adding webhooks, and tracking RevenueCat imports. Tool names mirror RevenueCat's MCP tools, so existing prompts work unchanged.
      38
      26 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Universal CLI and MCP server providing unified payment links, customer prefilling, expiring checkouts, refund management, fee comparison, and HMAC-verified webhook proxying across Stripe, Razorpay, and LemonSqueezy.
      7
      8 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct entity-action pair (e.g., get vs list for customers, orders, etc.), and there is no overlap. The only specific variant is get_product_variants, which is clearly a sub-resource.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, create_), with no deviations or mixed conventions.

    Tool Count5/5

    17 tools cover the main entities of the Lemon Squeezy platform (customers, orders, subscriptions, products, stores, webhooks, license keys, checkout) without being excessive. The scope is well-matched to a commerce API.

    Completeness2/5

    The tool set is heavily read-oriented with only two create operations (checkout and webhook). Missing update, delete, and other mutation operations for most entities (e.g., customers, products, stores) creates significant gaps that would hinder agents needing full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing