Bring Digital Products
to CrewAI
Learn how to connect Hotmart to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hotmart MCP Server?
Connect your Hotmart account to any AI agent and manage your digital product business through natural conversation.
What you can do
- Product Catalog — List all your digital products (courses, ebooks, memberships) with pricing and status
- Sales History — Browse all transactions with status, buyer details, and commission breakdowns
- Revenue Summary — Get aggregated sales data including total revenue, number of sales, and average ticket
- Subscription Management — List all active subscriptions with renewal dates and payment status
- Student Tracking — Browse all enrolled students and inspect individual course completion progress
How it works
1. Subscribe to this server
2. Enter your Hotmart Client ID and Client Secret from the developer portal
3. Start managing your products from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Digital Creators — monitor product sales, track student engagement, and review revenue without opening the Hotmart dashboard
- Course Authors — check student progress, identify drop-off points, and manage subscriber lists
- Affiliate Managers — review sales commissions, track affiliate performance, and audit transaction histories
Built-in capabilities (6)
Get sales history
Get sales summary
Get progress for a student
List all your products
List students (members)
List active subscriptions
Why CrewAI?
When paired with CrewAI, Hotmart becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hotmart tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Hotmart in CrewAI
Hotmart and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hotmart to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hotmart in CrewAI
The Hotmart MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Hotmart for CrewAI
Every tool call from CrewAI to the Hotmart MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I track how many students completed my course?
Yes. Use list_students to see all enrolled students across your products. Then use get_student_progress with a Student ID to see their course completion percentage, modules accessed, and last activity date. This helps identify students at risk of dropping off.
Does Hotmart require two credentials for authentication?
Yes. Hotmart uses OAuth 2.0 Client Credentials flow. You need a Client ID and a Client Secret, generated in the Hotmart Developer Portal. These are used to obtain a Bearer token automatically — the server handles token exchange internally.
Can I view a detailed breakdown of my sales revenue?
Yes. Use get_sales_summary for aggregated data including total revenue, number of sales, and average ticket. Use get_sales_history for individual transactions with status, price breakdowns, commissions, and buyer information. Combine with list_products to correlate revenue per product.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.