Lemon Squeezy MCP integration for AI agents.
Connect AI agents to Lemon Squeezy through 16 structured actions, including list customers, create customer, and delete webhook. Review authentication, input…
- ACTION CONTRACTS
- 16
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Lemon Squeezy integration exposes
The Lemon Squeezy Agent App exposes 16 provider-backed actions for productivity and finance work. Its current contract lets an authorized agent list lemon squeezy customers with optional store or email filtering, create a lemon squeezy customer for the specified store, and delete a lemon squeezy webhook by id. the returned acknowledgement is generated locally because lemon squeezy responds with 204 no content. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Lemon Squeezy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Lemon Squeezy capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_customersREADList Lemon Squeezy customers with optional store or email filtering.
INPUTS: storeId / email / pageNumber / pageSize
create_customerWRITECreate a Lemon Squeezy customer for the specified store.
INPUTS: storeId / name / email / city / region
delete_webhookHIGH IMPACTDelete a Lemon Squeezy webhook by ID. The returned acknowledgement is generated locally because Lemon Squeezy responds with 204 No Content.
INPUTS: webhookId
create_webhookWRITECreate a Lemon Squeezy webhook for the specified store.
INPUTS: storeId / url / events / secret
list_ordersREADList Lemon Squeezy orders with optional store, email, or order-number filtering.
INPUTS: storeId / userEmail / orderNumber / pageNumber / pageSize
list_productsREADList Lemon Squeezy products with optional store filtering and pagination.
INPUTS: storeId / pageNumber / pageSize
list_storesREADList stores that belong to the authenticated Lemon Squeezy account.
list_subscriptionsREADList Lemon Squeezy subscriptions with optional filters and pagination.
INPUTS: storeId / orderId / orderItemId / productId / variantId
list_variantsREADList Lemon Squeezy variants with optional product filtering and pagination.
INPUTS: productId / status / pageNumber / pageSize
list_webhooksREADList Lemon Squeezy webhooks with optional store filtering and pagination.
INPUTS: storeId / pageNumber / pageSize
retrieve_authenticated_userREADRetrieve the currently authenticated Lemon Squeezy user.
retrieve_customerREADRetrieve a single Lemon Squeezy customer by ID.
INPUTS: customerId
INPUT CONTRACTS
Know what the action needs before it runs.
list_customers
storeIdOPTIONAL- The Lemon Squeezy store ID.
emailOPTIONAL- Only return customers for this email.
pageNumberOPTIONAL- Page number to return.
pageSizeOPTIONAL- Number of items to return per page.
create_customer
storeIdREQUIRED- The Lemon Squeezy store ID.
nameREQUIRED- Full name of the customer.
emailREQUIRED- Email address of the customer.
cityOPTIONAL- City of the customer.
regionOPTIONAL- Region or state of the customer.
delete_webhook
webhookIdOPTIONAL- The Lemon Squeezy webhook ID.
create_webhook
storeIdOPTIONAL- The Lemon Squeezy store ID.
urlOPTIONAL- Webhook endpoint URL.
eventsOPTIONAL- Webhook events that should trigger deliveries.
secretOPTIONAL- Signing secret used to verify webhook deliveries.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Customers
List Lemon Squeezy customers with optional store or email filtering. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_customersControl Create Customer
Create a Lemon Squeezy customer for the specified store. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with List Orders
List Lemon Squeezy orders with optional store, email, or order-number filtering. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_ordersSAFETY BOUNDARY
Operate Lemon Squeezy with explicit limits
- Authorize Lemon Squeezy with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_webhook` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Lemon Squeezy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Lemon Squeezy task completed successfully.
CONNECTION MODEL
API key
Lemon Squeezy API key used with the Authorization Bearer header. Create it in Settings > API: https://docs.lemonsqueezy.com/guides/developer-guide/getting-started
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 11
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Lemon Squeezy.