Lemon Squeezy MCP Server
Related Servers
Alternatives to Lemon Squeezy MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceLets AI agents and shell users inspect products, sales, subscribers, offers and license contexts, then run explicitly confirmed commerce effects such as refunds, shipping updates, access changes and credential rotation against separate named seller profiles. License reads are performed without consuming a use, work is executed as exactly reviewed ordered batches that stop on the first failure, and exports stay bounded with caps and resume offsets.57401 npmAGPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
- FlicenseNot gradedqualityBmaintenanceCommerceOps MCP Server is an AI-native Model Context Protocol server for e-commerce operations, enabling AI agents to autonomously diagnose and resolve operational exceptions such as stuck orders, missed payment webhooks, warehouse delays, and oversold inventory, with built-in safety guardrails and audit logging.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to securely search products, obtain signed quotes, create checkouts, and track orders without directly handling prices or payment amounts, enforcing spending policies and audit trails.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover products, verify signed catalog feeds, negotiate within published policies, and place mandate-bound orders with signed receipts via MCP, A2A, or REST.1MIT
TDQS
Scored across 65 tools
Most tools are clearly distinct list/get/create/update/delete operations on well-separated resources (products, orders, subscriptions, licenses, etc.). A few meta tools (preview/submit_commerce_batch, export_resources, get_operation_schema) and usage-related tools (get_usage_record vs get_subscription_item_current_usage) could cause minor confusion, but descriptions differentiate them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_product, list_orders, create_checkout, update_subscription, cancel_subscription). Even the specialized tools (validate_license, submit_commerce_batch) follow this convention.
65 tools is heavy, but the server wraps a comprehensive e-commerce platform API covering ~15 distinct resources, so many tools are justified. However, the count is still high enough to risk selection complexity and could benefit from consolidation.
Core CRUD is present for customers, subscriptions, license keys, webhooks, and discounts, but several resources lack create/update/delete operations (e.g., products, variants, prices, files). Notable gaps will prevent agents from fully managing a store through this server alone.