Bring Omnichannel Support
to VS Code Copilot
Learn how to connect Kustomer to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Kustomer MCP Server?
Connect your AI agent to Kustomer to streamline your support operations and customer data auditing.
Key Features
- Omnichannel Conversation Access — List and audit support conversations from email, chat, and social channels
- Customer 360 View — Fetch detailed customer profiles including custom attributes and history
- Message Auditing — Retrieve the full message history for any support interaction
- Timeline Search — Perform deep searches across customer timelines using complex JSON filters
- Service Context — List support queues, agents, and custom data classes (Klasses)
Simple Setup
1. Subscribe to this server
2. Log in to Kustomer and generate a Bearer API Key (Settings > Security > API Keys)
3. Enter your key in the configuration panel
4. Start managing your support data via natural language
Built-in capabilities (10)
Check the status of the Kustomer API
Get details for a specific conversation
Get details for a specific customer
List all messages in a conversation
List Kustomer custom data classes (Klasses)
List all support agents (users)
Essential for identifying customer IDs for support auditing. List all customers in Kustomer
List recent support conversations
g., Billing, Technical Support) defined in Kustomer. List active support queues
Provide filters as a JSON string. Perform a deep search across the customer timeline
Why VS Code Copilot?
GitHub Copilot Agent mode brings Kustomer data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
Kustomer in VS Code Copilot
Kustomer and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Kustomer 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 Kustomer in VS Code Copilot
The Kustomer 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 10 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
Kustomer for VS Code Copilot
Every tool call from VS Code Copilot to the Kustomer MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Where do I find my Kustomer API Key?
Log in to Kustomer, navigate to Settings > Security > API Keys, and create a new key with the necessary scopes.
Can I see chat messages in real-time?
The list_conversation_messages tool fetches the current history. While not a streaming 'live' view, it provides the most recent state.
Does this support creating customers?
The current version focus on data retrieval and analysis. Creation tools are planned for future updates.
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.
