Bring Crisp
to LangChain
Learn how to connect Crisp to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Crisp through native MCP adapters. Connect 6 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Crisp MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Crisp queries for multi-turn workflows
Crisp in LangChain
Crisp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Crisp to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
