Lemon Squeezy Server
Related Servers
Alternatives to Lemon Squeezy Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.34 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the LemonSqueezy API. Enables managing stores, products, customers, subscriptions, discounts, and license keys from any MCP-compatible AI assistant.64440 npm4MIT
- AlicenseBqualityDmaintenanceUniversal Semantic Bridge for Lemon Squeezy: A high-performance Model Context Protocol (MCP) server that empowers AI assistants (Cursor, Claude, VS Code) to query payments, manage subscriptions, and sync customers to Salesforce directly from your editor. 🍋✨5346 npm3MIT
- AlicenseAqualityAmaintenanceUniversal 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.714 npmMIT

Subotiz MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage subscriptions, usage-based billing, payments, refunds, tax compliance, and invoicing to drive revenue growth.1MIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents and human operators to manage Stripe payment operations, SaaS billing, subscriptions, refunds with safety caps, and Austrian/EU tax compliance including VAT and BAO record retention.1-
TDQS
Scored across 17 tools
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.
All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, create_), with no deviations or mixed conventions.
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.
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.