mcp-server-creem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREEM_API_KEY | Yes | Your Creem API key | |
| CREEM_TEST_MODE | No | Set to 'true' to use test mode | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_productB | Create a new product in Creem. Products can be one-time payments or recurring subscriptions. |
| get_productA | Retrieve details of a specific product by ID |
| search_productsC | Search and list all products |
| create_checkoutB | Create a checkout session for a product. Returns a checkout URL to redirect customers to. |
| get_checkoutA | Retrieve checkout session details by ID |
| get_customerA | Retrieve customer details by email or customer ID |
| list_customersC | List all customers |
| create_customer_portal_linkA | Generate a customer portal login link for a customer to manage their subscriptions |
| get_subscriptionA | Retrieve subscription details by ID |
| cancel_subscriptionC | Cancel an active subscription |
| update_subscriptionC | Update subscription (e.g., change number of seats/units) |
| upgrade_subscriptionC | Upgrade or downgrade a subscription to a different product |
| activate_licenseB | Activate a license key for a specific instance/device |
| deactivate_licenseB | Deactivate a license key instance |
| validate_licenseB | Validate if a license key is active and valid |
| create_discountB | Create a discount code |
| get_discountC | Retrieve discount code details |
| delete_discountC | Delete a discount code |
| search_transactionsC | Search and list transactions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool targets a distinct action (activate, deactivate, validate, cancel, update, upgrade, create, get, list, search) on a specific resource (license, subscription, checkout, discount, product, customer, transaction). There is no overlap in functionality, and descriptions clearly differentiate them.
All tool names follow a consistent verb_object pattern with underscores (e.g., activate_license, create_checkout, list_customers). The verbs are varied but always come first, and the naming is predictable across the entire set.
19 tools cover the essential operations for a payment, subscription, and licensing platform without being excessive. Each tool serves a clear purpose, and the count is well-scoped for the domain.
The tool surface covers core CRUD and lifecycle operations for products, subscriptions, licenses, discounts, and customers. Minor gaps exist (e.g., no product update/delete, no direct subscription creation via tool), but these are acceptable given the checkout-based flow.