Bring Crisp
to CrewAI
Learn how to connect Crisp 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 Crisp MCP Server?
Connect your Crisp account to any AI agent and take full control of your multi-channel customer support and visitor engagement workflows through natural conversation.
What you can do
- Conversation Orchestration — List and manage active chat and email support sessions programmatically, including monitoring unread counts and conversation status in real-time
- Automated Messaging — Programmatically dispatch text messages to active sessions to coordinate immediate customer assistance and engagement
- Thread Intelligence — Access complete message histories for any session to provide high-fidelity context for your support and marketing responses
- Visitor Lifecycle — Retrieve detailed visitor profiles and people records to maintain a perfectly coordinated relationship history
- Operational Monitoring — Access real-time website traffic metrics and support volume summaries directly through your agent for instant CX reporting
How it works
1. Subscribe to this server
2. Retrieve your Plugin ID, Plugin Key, and Website ID from the Crisp dashboard
3. Start managing your omnichannel support from Claude, Cursor, or any MCP client
No more manual ticket shuffling or missing messages in busy chat windows. Your AI acts as your dedicated support engineer and visitor engagement coordinator.
Who is this for?
- Support Teams — instantly respond to visitor queries and summarize conversation threads using natural language commands
- Customer Success — monitor visitor engagement and retrieve high-fidelity profile metadata without leaving your workspace
- Growth Marketers — automate personalized outreach to active visitors and track website traffic through simple AI queries
Built-in capabilities (6)
Get conversation details
List messages in a conversation
Get visitor profile details
List all website conversations
List all website visitors/people
Pass data as a JSON string. Send a message to a conversation
Why CrewAI?
When paired with CrewAI, Crisp becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Crisp 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
Crisp in CrewAI
Crisp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Crisp 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 Crisp in CrewAI
The Crisp 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
Crisp for CrewAI
Every tool call from CrewAI to the Crisp 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 Crisp API credentials?
Go to your Crisp dashboard, navigate to the Marketplace, create a new plugin, and you will find your Plugin ID and Plugin Key.
What is the Website ID?
The Website ID is a unique UUID found in your Settings > Website Settings section in Crisp.
Can I retrieve messages from past sessions?
Yes! The get_messages tool allows the agent to retrieve the complete transcript for any session ID in your history.
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.