Bring Shared Inbox
to Cursor
Learn how to connect Front to Cursor 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 Cursor?
Cursor's Agent mode turns Front into an in-editor superpower. Ask Cursor to generate code using live data from Front and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Front in Cursor
Front and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Front to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.