Bring Shared Inbox
to VS Code Copilot
Learn how to connect Front to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Front MCP Server?
Connect your Front account to any AI agent and take full control of your team's customer communication and shared inbox workflows through natural conversation.
What you can do
- Conversation Orchestration — List and manage customer conversations programmatically, including updating statuses (open, archived, spam) and assigning teammates
- Message Intelligence — Retrieve complete message histories and metadata for any conversation to perform deep analysis and sentiment tracking
- Omnichannel Support — Monitor multiple communication streams including Email, Chat, and SMS from a single unified AI interface
- Team Collaboration — Manage team contacts and retrieve teammate profiles to coordinate internal routing and workload distribution
- Operational Visibility — Get a comprehensive overview of shared inboxes and active channels using natural language commands
How it works
1. Subscribe to this server
2. Retrieve your API Token from Front (Settings > Developers > API Tokens)
3. Start managing your unified inbox from Claude, Cursor, or any MCP client
No more manual toggling between different communication channels. Your AI acts as your dedicated support and communication coordinator.
Who is this for?
- Support Teams — instantly triage high-volume inboxes and assign urgent conversations using natural language
- Customer Success Managers — retrieve full interaction histories and update contact details without leaving your workspace
- Operations Leads — monitor channel activity and manage team assignments across shared mailboxes
Built-in capabilities (12)
Check connection
Get contact details
Get conversation info
Read message details
). List communication channels
Get message history
List team conversations
List team inboxes
List your contacts
Send a message
Find conversations
Modify conversation
Why VS Code Copilot?
GitHub Copilot Agent mode brings Front data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 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
Front in VS Code Copilot
Front and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Front 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 Front in VS Code Copilot
The Front 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 12 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
Front for VS Code Copilot
Every tool call from VS Code Copilot to the Front 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 create an API Token in Front?
Log in to Front, go to Settings > Developers > API Tokens, and click Create Token. Ensure you select the appropriate scopes for your needs.
Can I search for conversations by status?
Yes! The list_conversations tool allows you to filter results by statuses like 'open', 'archived', 'deleted', or 'spam'.
How do I send a reply via AI?
Use the reply_to_conversation tool by providing the conversationId and your message body. You can also specify an author_id to send as a specific teammate.
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.