Hotmart MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Hotmart MCP Server show my top 5 products by sales"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hotmart MCP Server
Servidor MCP (Model Context Protocol) para integração com APIs da Hotmart. Este servidor permite que agentes de IA gerenciem produtos, vendas e outras operações da Hotmart através de uma interface padronizada.
📋 Sobre
O Hotmart MCP Server é uma implementação do Model Context Protocol que conecta o Claude (e outros LLMs) diretamente às APIs da Hotmart. Desenvolvido com arquitetura modular e suporte a múltiplos transportes (STDIO local e SSE web), oferece uma integração robusta e flexível para automação de operações de produtores digitais.
Related MCP server: hotmart-mcp
📋 Pré-requisitos
Python 3.11 ou superior
Conta Hotmart com credenciais de API
uv (recomendado) ou pip para gerenciamento de dependências
Claude Desktop (para uso local) ou navegador web (para uso SSE)
🚀 Instalação
1. Clonar o Repositório
git clone https://github.com/cajuflow/hotmart-mcp.git
cd hotmart-mcp2. Instalar Dependências
uv sync3. Configurar Variáveis de Ambiente
# Copiar arquivo de exemplo
cp .env.example .env
# Editar com suas credenciais
nano .envConteúdo do .env:
# Credenciais Hotmart (obrigatório)
HOTMART_CLIENT_ID=seu_client_id_aqui
HOTMART_CLIENT_SECRET=seu_client_secret_aqui
HOTMART_BASIC_TOKEN=seu_basic_token_aqui
# Ambiente da Hotmart (sandbox ou production)
HOTMART_ENVIRONMENT=sandbox
# Configuração MCP (sse ou stdio)
TRANSPORT_TYPE=stdio
# Host e Porta para SSE Transport
MCP_HOST=0.0.0.0
MCP_PORT=8000⚙️ Configuração Avançada
Host e Porta do Servidor
Para uso com Docker ou SSE transport, configure:
# Docker/Container (aceita conexões externas)
MCP_HOST=0.0.0.0
MCP_PORT=8000
# Local apenas (default)
MCP_HOST=127.0.0.1
MCP_PORT=8000Uso comum por ambiente:
Local/STDIO:
MCP_HOST=127.0.0.1(padrão)Docker/Container:
MCP_HOST=0.0.0.0(obrigatório)Cloud/Produção:
MCP_HOST=0.0.0.0(recomendado)
4. Integração com Claude Desktop
Adicione ao seu claude_desktop_config.json:
stdio:
{
"mcpServers": {
"hotmart": {
"command": "python",
"args": ["C:/hotmart-mcp/hotmart_mcp.py"],
"env": {
"HOTMART_CLIENT_ID":"",
"HOTMART_CLIENT_SECRET":"",
"HOTMART_BASIC_TOKEN":"",
"HOTMART_ENVIRONMENT": "production"
}
}
}
}5. Executar o Servidor
# Modo STDIO (padrão - Claude Desktop)
uv run python hotmart_mcp.py
# Modo SSE (aplicações web)
TRANSPORT_TYPE=sse uv run python hotmart_mcp.py6. Docker (Opcional)
# Build da imagem
docker build -t hotmart-mcp .
# Executar container (usa .env automático)
docker run -p 8000:8000 --env-file .env hotmart-mcp
# Testar conectividade
python test_sse_poc.pyImportante: Para Docker, certifique-se que MCP_HOST=0.0.0.0 no .env!
Log esperado (Docker funcionando):
-> Running in SSE mode on 0.0.0.0:8000
INFO: Uvicorn running on http://0.0.0.0:8000🛠️ Ferramentas Disponíveis
get_hotmart_products: Lista produtos da sua conta Hotmart com filtros avançados.get_hotmart_sales_history: Obtém histórico de vendas com filtros detalhados.
Testes
uv run python test_runner.py all🆘 Suporte
📧 Email: contato@vdscruz.com
🐛 Issues: GitHub Issues
Desenvolvido com ❤️ pela Cajuflow
Empoderando criadores digitais com soluções inteligentes de automação.
Available Tools
2 toolsget_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
Inputs: status, max_results, page_token, product_id, +1 more. Returns: result
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
Inputs: transaction_status, max_results, page_token, product_id, +9 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Build and manage AI-native customer support agents from Claude or any MCP client.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol implementation with a modular architecture that exposes capabilities through specialized agents, enabling seamless integration with Claude Desktop and web applications.2-
- AlicenseCqualityDmaintenanceEnables querying Hotmart sales, subscriptions, members area, products, and coupons via natural language, and performing actions like creating coupons or refunding sales.4014MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.4-
- AlicenseCqualityDmaintenanceEnables AI agents to manage Kommo CRM (formerly AmoCRM) entities including leads, contacts, companies, tasks, notes, pipelines, and products through natural language commands via the Model Context Protocol.3931 npm1MIT