Creem
Creem is a merchant-of-record platform for managing products, checkouts, subscriptions, customers, licenses, discounts, transactions, refunds, and revenue operations.
Verdict
Common use cases
- Generate checkout links during sales calls
- Cancel subscriptions from support tickets
- Activate license keys for new customers
- Close credit accounts after refunds
- Create customer portal links on demand
Integration
- Vendor
- Creem
- Category
- other
- Auth
- API_KEY
- Tools
- 48
- Composio slug
creem
Tools
- Activate License
Activate a Creem license key for a named device or instance. This mutates the license entitlement by consuming an activation slot and can prevent other devices from activating when the license reaches its limit.
- Archive Product
Archive a product so it can no longer be purchased. This is a destructive soft-delete: the product remains available for historical orders and subscriptions.
- Cancel Subscription
Cancel an active Creem subscription immediately, at the end of its current billing period, or according to the store default. This is a destructive financial operation; confirm the subscription and timing before calling.
- Close Credit Account
Experimental Creem API: permanently close a credit account in the connected production store. This irreversible action cannot be undone; confirm the account ID before calling.
- Create Checkout
Create a live checkout session in the connected Creem production store for a one-time payment or subscription. The returned checkout_url can accept a real customer payment. custom_price overrides the product's per-unit price for this checko
- Create Credit Account
Experimental Creem API: create a credit account for a customer in the connected production store, optionally with an initial balance. This is a live financial mutation. Verify the customer ID and initial balance before calling because a suc
- Create Customer
Create a customer record in the connected Creem production store. This is a live production mutation: a successful call permanently adds a customer.
- Create Customer Portal Link
Generate a sensitive customer portal link for managing billing, subscriptions, and payment methods in the connected Creem production store. Share the returned URL only with the intended customer.
- Create Discount
Create a promotional discount for products in the connected Creem production store. This is a live financial mutation that can reduce customer prices. Confirm the product IDs, fixed amount and currency, or percentage before calling.
- Create Product
Create a product in the connected Creem production store for a one-time payment, free purchase, or subscription. This is a live financial mutation: a successful call creates a purchasable product. Use idempotency_key for safe retries.
- Credit Account
Experimental Creem API: add credits to a customer credit account in the connected production store and return the resulting ledger transaction. This is an irreversible live financial mutation. Confirm the account, amount, and reference befo
- Deactivate License
Deactivate one device instance for a Creem license key and free its activation slot. This removes that instance's entitlement and access; confirm both the license key and instance ID before calling.
- Debit Account
Experimental Creem API: irreversibly deduct credits from a customer credit account in the connected production store and create a live ledger transaction. Confirm the account, amount, and reference before calling. For retries, reuse the sam
- Delete Discountdestructive
Permanently delete a Creem discount code and prevent any further use. This destructive financial operation cannot be undone; confirm the discount ID before calling.
- Freeze Credit Account
Experimental Creem API: freeze a credit account in the connected production store, preventing new transactions against its live credit balance. This changes financial account state; confirm the account ID before calling.
- Get Affiliate
Retrieve a single affiliate by ID, including referral link, click and conversion counts, and lifetime commission.
- Get Checkout
Retrieve a Creem checkout session by ID, including its status, product, customer, payment relationships, issued licenses, and metadata.
- Get Credit Account
Experimental Creem API: retrieve a customer credits account by its unique identifier, including its owner, unit label, status, and timestamps.
- Get Credit Account Balance
Experimental Creem API: retrieve a credit account's current projected balance or its balance at an optional historical timestamp.
- Get Customer
Retrieve one Creem customer by exactly one lookup field: customer_id or email. Returns the customer's profile and metadata.
- Get Discount
Retrieve Creem discount details by exactly one lookup field: discount_id or discount_code. Returns usage limits, expiration, and discount amount.
- Get Product
Retrieve a single Creem product by its unique identifier.
- Get Store Metrics
Retrieve Creem store counts, revenue, and monthly recurring revenue in integer cents, optionally filtered and grouped by a date range.
- Get Subscription
Retrieve a Creem subscription by ID, including its status, billing cycle, customer, product, items, payment history, and timestamps.
- Get Transaction
Retrieve a single Creem transaction by ID, including payment amounts, status, tax details, and associated resource IDs.
- List Affiliate Commissions
Retrieve one page of an affiliate's commissions, optionally filtered by pending, approved, or paid settlement status.
- List Affiliates
Retrieve one page of joined Creem affiliates with referral links, click and conversion counts, and lifetime commission. Invited affiliates who have not joined a program are not included.
- List Credit Account Entries
Experimental Creem API: retrieve one page of a credit account's credit and debit history, with forward or backward ID-based pagination.
- List Credit Accounts
Experimental Creem API: list customer credit accounts for the authenticated store, excluding system accounts. Returns one page at a time. The response and cursor contract may change while this API remains experimental.
- List Customer Licenses
Retrieve one page of license keys for a specific Creem customer. Returns pagination totals and an opaque cursor when another page is available.
- List Customer Orders
Retrieve one page of orders for a specific customer, including monetary details, statuses, related resource IDs, and pagination totals.
- List Customers
Retrieve one page of customers, including customer details and pagination totals. Use next_cursor to continue through additional pages.
- List Discounts
Search and retrieve one page of Creem discounts, optionally filtered by product, status, type, or creation date.
- List License Instances
Retrieve one page of activated instances for a Creem license. Use an instance ID from the response when deactivating a specific instance.
- List Products
Search and retrieve one page of Creem products, optionally filtered by lifecycle status. Returns an opaque cursor when another page is available.
- List Subscriptions
Retrieve one page of Creem subscriptions across the store or for one customer, including product, customer, billing, transaction, and pagination details.
- List Transactions
Search and retrieve one page of Creem payment transactions, optionally filtered by customer, order, or product.
- Pause Subscription
Pause a Creem production subscription immediately or after its current billing period, stopping live billing while retaining it for later resumption. Confirm the subscription and timing before calling.
- Refund Payment
Issue an irreversible full refund of a payment's entire remaining refundable amount using its transaction ID. Partial refunds are not supported. Confirm the transaction before calling. A `pending` or `requiresAction` response is non-termina
- Resume Subscription
Resume a paused or scheduled-cancel Creem production subscription. This changes live subscription billing; confirm the subscription before calling.
- Reverse Credit Transaction
Experimental Creem API: reverse a previous credit or debit in the connected production store by creating a new compensating transaction; the original transaction remains in the ledger. This is an irreversible live financial mutation. Confir
- Screen Prompt
Evaluate a text prompt against Creem content policies before generation. Warning: this endpoint is experimental and its request, response, or behavior may change without stability guarantees.
- Unfreeze Credit Account
Experimental Creem API: unfreeze a frozen credit account in the connected production store, allowing live credit and debit transactions again. Confirm the account ID before calling. Closed accounts and accounts that are not frozen cannot be
- Update Customer
Update the name or metadata of an existing customer in the connected Creem production store. Only supplied fields change; provide at least one change.
- Update Product
Update at least one field on a product in the connected Creem production store. Only supplied fields change; pricing, currency, billing, and tax changes affect future purchases, and changing the price creates a new default price.
- Update Subscription
Update items, units, seats, or add-ons on a Creem production subscription. This changes live recurring billing; proration-charge-immediately can charge the customer immediately.
- Upgrade Subscription
Upgrade a subscription to a different product or plan in Creem production. This changes live billing and may charge the customer: the default update behavior applies proration and can charge it immediately.
- Validate License
Verify that a Creem license key is valid and active for a specific instance, including its activation status and expiration.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP' and select Creem from the list. 3. You'll be prompted to paste a Creem API key — generate one from your Creem dashboard under Settings > API Keys. 4. Grant the key full read-write access if you want to create checkouts and cancel subscriptions; read-only if you only need to query data. 5. Paste the key into Switchy and click 'Connect'. 6. Switchy will confirm the connection and show you which Creem store is linked. 7. To test, open any Project and type '@Creem list my products' — the MCP should return your catalog. 8. To invoke a tool, @mention Creem in a message and describe the task (e.g. '@Creem create a checkout for product XYZ'). 9. The assistant will call the appropriate tool and return the result inline.
What teammates see: by default, memories from Creem are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Checkout Link
@Creem create a checkout session for product ID prod_abc123 with a custom price of $49. Return the checkout URL.
Cancel Subscription
@Creem cancel subscription sub_xyz789 at the end of the current billing period. Confirm the cancellation date.
Activate License Key
@Creem activate license key lic_456def for device named 'MacBook Pro 2023'. Show remaining activations.
Generate Portal Link
@Creem create a customer portal link for customer ID cus_111aaa. Return the URL and expiration time.
Archive Old Product
@Creem archive product ID prod_legacy99 so it no longer appears in the store. Confirm the archive timestamp.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@creem show me all active subscriptions for customer cus_abc123 and summarize their total monthly recurring revenue
Found 3 active subscriptions for customer cus_abc123: 1. Pro Plan (sub_xyz789) – $49/month, renews March 15 2. Enterprise Add-on (sub_def456) – $99/month, renews March 20 3. Storage Pack (sub_ghi012) – $15/month, renews March 18 Total MRR from this customer: $163/month. All subscriptions are in good standing with no failed payments in the last 90 days. The Pro Plan has been active for 14 months; the other two were added within the last quarter.
This example demonstrates read-only subscription querying and AI synthesis of billing data. Requires API key with read:subscriptions scope. The MCP returns structured subscription objects; the AI aggregates them into business metrics. No side effects.
@creem create a checkout session for product prod_premium with a custom price of $299 one-time, and include customer email support@acme.com
Checkout session created successfully: Checkout URL: https://creem.io/checkout/cs_live_a1b2c3d4e5f6 Product: Premium License (prod_premium) Price: $299.00 (one-time, overriding default $349) Customer email: support@acme.com (pre-filled) Expires: 24 hours from now This is a live production checkout link. When the customer completes payment, Creem will fulfill the order and send a receipt to the provided email. The custom price override has been applied.
This is a write operation that generates a real payment link in your production Creem store. The checkout URL can accept actual customer payments. Confirm product ID and pricing before sharing the link. The session expires after 24 hours if unused.
@creem cancel subscription sub_xyz789 at the end of the current billing period and draft a cancellation confirmation email explaining the customer will retain access until March 15
Subscription sub_xyz789 (Pro Plan) has been scheduled for cancellation at period end. Cancellation effective: March 15, 2025 (end of current billing cycle) No refund issued (period already paid) Customer retains full access until March 15 --- Draft confirmation email: Subject: Your Pro Plan subscription will end on March 15 Hi there, We've processed your cancellation request. Your Pro Plan subscription will remain active until March 15, 2025—the end of your current billing period. You'll continue to have full access to all Pro features until that date. No further charges will be made. If you change your mind, you can reactivate anytime before March 15 from your account dashboard. Thanks for being a customer.
This combines a destructive financial operation (canceling a subscription) with AI drafting. The cancel action is irreversible once executed; confirm the subscription ID and timing before running. Requires write:subscriptions scope. The AI-generated email is a starting point—review tone and policy details before sending.
Use-case deep-dives
When your support team needs to issue refunds and cancel seats
A 6-person B2B SaaS company runs customer support in Slack and needs agents to cancel subscriptions, issue credits, and generate portal links without opening the Creem dashboard. This MCP is the right call if your support volume is under 50 tickets/week and your team already uses Switchy for shared context—agents can cancel a subscription or create a credit account in the same thread where they're troubleshooting the customer issue. The 48-tool surface means you'll configure scopes carefully: most support teams only need Cancel Subscription, Create Credit Account, and Create Customer Portal Link. If your support load is higher or you need audit trails beyond chat history, a dedicated helpdesk integration beats an MCP. For small teams who want billing mutations in the same workspace as everything else, Creem in Switchy closes the loop.
Why this MCP works for self-serve software activation
A 3-person dev-tools startup sells desktop licenses and needs to activate keys when customers email proof of purchase or hit a Slack webhook from Stripe. The Activate License tool lets the founder or a part-time ops person provision seats without context-switching to Creem's admin panel. This scenario wins when activation volume is under 20/day and the team values speed over ceremony—Switchy becomes the single pane where you read the customer message, verify payment in another tool, and activate the license in one thread. The boundary: if you're activating hundreds of licenses daily or need programmatic batch operations, a backend script calling Creem's API directly is faster and safer. For low-volume, high-touch onboarding where a human confirms each activation, this MCP keeps the workflow in chat and the API key scoped to one person.
When marketing needs to archive SKUs without engineering
A 5-person e-learning company launches a new course bundle every quarter and needs to archive old products so customers don't buy deprecated tiers. The marketing lead uses the Archive Product tool in Switchy to soft-delete SKUs the morning of launch, coordinating with the founder in the same thread where they're drafting the announcement email. This MCP is the right fit if your catalog changes are infrequent (monthly or less) and you want non-technical teammates to execute them without a Jira ticket to engineering. The trade-off: Creem's 48-tool surface includes destructive mutations like Close Credit Account, so you'll lock down the API key to one trusted person and document which tools are safe for async use. If your product catalog changes daily or you need rollback logic, a staging environment and a proper release process beats ad-hoc mutations in chat. For small teams shipping quarterly, this keeps launch day fast.
Frequently asked
What does the Creem MCP do in Switchy?
It connects your Creem license and subscription store to Switchy so AI can create checkouts, activate licenses, manage subscriptions, and handle customer accounts. All 48 tools operate on your live production store — when AI creates a checkout or cancels a subscription, it's a real financial transaction. Use it to automate billing workflows, provision software licenses, or let support agents handle refunds without leaving the chat.
Do I need admin access to connect Creem?
Yes. The MCP uses an API key with write access to your production Creem store, so only account owners or billing admins should generate and install the key. Anyone on your Switchy workspace can then invoke the tools, but you control which team members see the integration in your workspace settings. Treat the API key like a database password — it can create checkouts, cancel subscriptions, and close credit accounts.
Can the Creem MCP refund a customer payment?
No. The 48 tools cover checkout creation, subscription management, license activation, and customer records, but refunds aren't exposed. You'll still need to log into the Creem dashboard or use their REST API directly for refunds. The MCP focuses on forward-moving transactions — creating checkouts, activating licenses, canceling subscriptions — not reversing completed payments.
How is this different from using Creem's dashboard?
The MCP lets AI execute Creem operations mid-conversation — a support agent can cancel a subscription or generate a customer portal link without switching tabs. The dashboard is still necessary for refunds, analytics, and bulk operations. Think of the MCP as a faster path for one-off transactional tasks that happen during customer interactions, not a replacement for financial reporting or store configuration.
Who on the team should connect the Creem integration?
Your billing admin or whoever owns the Creem account. They generate the API key and paste it into Switchy once. After that, you decide which workspace members can invoke the tools — typically support leads, account managers, or engineers who provision licenses. Because every tool hits production, limit access to people who understand the financial and legal consequences of canceling subscriptions or closing credit accounts.