Compatible with every major AI agent and IDE
What is the Whop MCP Server?
Connect your Whop account to any AI agent to automate your digital commerce and membership operations. Whop provides an all-in-one platform for selling digital access, managing subscriptions, and tracking customer payments through natural conversation.
What you can do
- Product Orchestration — List and manage your digital products and subscription plans with detailed pricing metadata.
- Membership Management — Retrieve active user memberships, monitor subscription statuses, and process cancellations programmatically.
- Financial Monitoring — Track payment histories and retrieve customer invoices directly from the AI interface to monitor revenue streams.
- Marketing Automation — Create and manage promo codes for your digital storefront to drive sales through natural language commands.
- Customer Experience — Monitor product reviews and user feedback to stay updated on your community's health.
How it works
- Subscribe to this server
- Enter your Whop Company API Key from your developer settings
- Start managing your digital storefront from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Digital Creators — manage software access and community memberships more efficiently without leaving the chat.
- E-commerce Operations — automate the tracking of payments, invoices, and promo codes.
- Community Managers — quickly check user membership statuses and process administrative tasks via natural conversation.
Built-in capabilities (11)
Cancel a user membership
Create a new promo code
Get current Whop user or company details
Get details for a specific membership
List customer invoices
List user memberships
List payment transactions
List all Whop subscription plans
List all Whop products
List promotional codes
List product reviews
Why CrewAI?
When paired with CrewAI, Whop becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Whop 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
Whop in CrewAI
Whop and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Whop 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 | 4,000+ 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 Whop in CrewAI
The Whop 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 11 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
Whop for CrewAI
Every tool call from CrewAI to the Whop MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Whop Company API Key?
Log in to your Whop dashboard, navigate to Settings > Developer, and you will find your unique Company API Key in the API section.
Can the agent process membership cancellations?
Yes! The cancel_membership tool allows your AI agent to programmatically end a user's subscription when requested.
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.
Explore More MCP Servers
View all →
OpenAlex Alternative
14 toolsAutomate scholarly research via OpenAlex — search millions of works, authors, and institutions directly from any AI agent.

CrossRef
3 toolsSearch 140M+ scholarly works across all scientific disciplines — with DOI resolution, citation counts, author lookup, and full bibliographic metadata from the world's largest DOI registry.

Besitos Corp
10 toolsIntegrate mobile gaming and rewards via Besitos — list games, track user activity, and manage offers directly from any AI agent.

Creatomate
9 toolsEquip your AI agent to automate video generation, rendering, and asset management via the Creatomate API.
