Hotmart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host para transporte SSE | 127.0.0.1 |
| MCP_PORT | No | Porta para transporte SSE | 8000 |
| TRANSPORT_TYPE | No | Tipo de transporte (stdio ou sse) | stdio |
| HOTMART_CLIENT_ID | Yes | Hotmart client ID (obrigatório) | |
| HOTMART_BASIC_TOKEN | Yes | Hotmart basic token (obrigatório) | |
| HOTMART_ENVIRONMENT | No | Ambiente da Hotmart (sandbox ou production) | sandbox |
| HOTMART_CLIENT_SECRET | Yes | Hotmart client secret (obrigatório) |
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_hotmart_productsA | Get list of products from Hotmart account. Args: status: Filter by product status. Options: DRAFT, ACTIVE, PAUSED, NOT_APPROVED, IN_REVIEW, DELETED, CHANGES_PENDING_ON_PRODUCT max_results: Maximum number of items per page (default: 50, max: 50) page_token: Cursor for pagination product_id: Unique identifier (ID) of the product (7 digits) format: Product format. Options: EBOOK, SOFTWARE, MOBILE_APPS, VIDEOS, AUDIOS, TEMPLATES, IMAGES, ONLINE_COURSE, SERIAL_CODES, ETICKET, ONLINE_SERVICE, ONLINE_EVENT, BUNDLE, COMMUNITY Returns: JSON string containing list of products with their details |
| get_hotmart_sales_historyA | Get sales history from Hotmart account. Args: transaction_status: Status da transação. Options: APPROVED, BLOCKED, CANCELLED, CHARGEBACK, COMPLETE, EXPIRED, NO_FUNDS, OVERDUE, PARTIALLY_REFUNDED, PRE_ORDER, PRINTED_BILLET, PROCESSING_TRANSACTION, PROTESTED, REFUNDED, STARTED, UNDER_ANALISYS, WAITING_PAYMENT max_results: Número máximo de itens por página (default: 50, max: 50) page_token: Cursor para paginação product_id: ID do produto (7 dígitos) start_date: Data inicial em milissegundos (timestamp desde 1970-01-01) end_date: Data final em milissegundos (timestamp desde 1970-01-01) sales_source: Código SRC da origem da venda transaction: Código único da transação (ex: HP17715690036014) buyer_name: Nome do comprador buyer_email: Email do comprador payment_type: Tipo de pagamento. Options: BILLET, CASH_PAYMENT, CREDIT_CARD, DIRECT_BANK_TRANSFER, DIRECT_DEBIT, FINANCED_BILLET, FINANCED_INSTALLMENT, GOOGLE_PAY, HOTCARD, HYBRID, MANUAL_TRANSFER, PAYPAL, PAYPAL_INTERNACIONAL, PICPAY, PIX, SAMSUNG_PAY, WALLET offer_code: Código da oferta commission_as: Como foi comissionado. Options: PRODUCER, COPRODUCER, AFFILIATE Returns: JSON string containing sales history with detailed information |
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 2 tools
Each tool targets a distinct domain (products vs sales history) with no overlap in purpose, making it easy for an agent to select the correct tool.
Both tools follow a consistent 'get_hotmart_<resource>' pattern, using snake_case and clear resource names.
With only 2 tools, the server feels too minimal for a comprehensive Hotmart API integration; typical MCP servers offer more functionality.
The tool surface is severely incomplete, providing only read operations for products and sales, with no create, update, or delete capabilities.