hotmart-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOTMART_BASIC | Yes | Basic auth token | |
| HOTMART_CLIENT_ID | Yes | OAuth client ID | |
| HOTMART_CLIENT_SECRET | Yes | OAuth client secret |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_salesC | List sales history |
| get_saleC | Get sale details |
| list_subscriptionsD | List subscriptions |
| cancel_subscriptionC | Cancel a subscription |
| list_productsC | List products |
| get_commissionC | Get commission summary |
| list_usersC | List users |
| refund_purchaseC | Refund a purchase |
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 8 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Hotmart domain, such as subscriptions, commissions, sales, products, and users. There is no overlap or ambiguity between tools like 'cancel_subscription' and 'list_subscriptions', or 'get_sale' and 'list_sales', making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'cancel_subscription', 'get_commission', and 'list_products'. This uniformity enhances readability and predictability, with no deviations in naming conventions across the toolset.
With 8 tools, the server is well-scoped for managing a Hotmart platform, covering key operations like sales, subscriptions, products, users, and refunds. Each tool serves a specific and necessary function without being overly sparse or bloated, fitting typical expectations for such a domain.
The toolset provides strong coverage for core Hotmart workflows, including CRUD-like operations for sales, subscriptions, products, and users, as well as actions like refunds and cancellations. A minor gap exists in update operations (e.g., updating a subscription or user details), but agents can likely work around this with the available tools.