Lemon Squeezy Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEMONSQUEEZY_API_KEY | No | Your Lemon Squeezy API key (alternative name) | |
| LEMON_SQUEEZY_API_KEY | No | Your Lemon Squeezy API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userB | Get the current authenticated Lemon Squeezy user. |
| list_storesA | List all Lemon Squeezy stores. |
| get_storeC | Get details of a specific store. Args: store_id: The ID of the store |
| list_productsB | List all products. |
| get_productC | Get a specific product by ID. Args: product_id: The ID of the product |
| get_product_variantsC | Get all variants for a given product ID. Args: product_id: The ID of the product to fetch variants for |
| list_ordersB | List all orders. |
| get_orderB | Get an order by ID. Args: order_id: The ID of the order |
| list_customersC | List all customers. |
| get_customerB | Get a customer by ID. Args: customer_id: The ID of the customer |
| list_subscriptionsB | List all subscriptions. |
| get_subscriptionB | Get a subscription by ID. Args: subscription_id: The ID of the subscription |
| list_license_keysA | List all license keys. |
| get_license_keyC | Get a license key by ID. Args: license_key_id: The ID of the license key |
| create_checkoutC | Create a Lemon Squeezy checkout session with full custom configuration. Args: data: The checkout data (see LemonSqueezy API docs) |
| create_webhookC | Register a webhook URL for a specific store and events. Args: webhook_data: The webhook data (see LemonSqueezy API docs) |
| list_webhooksA | List all webhooks. Optionally filter by store ID. Args: store_id: If provided, only webhooks for this store will be returned |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| audit://lemonsqueezy-operations |
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.