Bring Crisp
to VS Code Copilot
Learn how to connect Crisp to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Crisp data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Crisp in VS Code Copilot
Crisp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Crisp to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.