Bring Conversational Ai
to Cursor
Learn how to connect Intercom 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 Intercom MCP Server?
Connect your Intercom account to any AI agent and manage customer communications through natural conversation.
What you can do
- Contact Management — List contacts, inspect profiles with tags and custom attributes, and search by email or name
- Conversation Tracking — Browse all conversations, inspect threads with full message history, and monitor status
- Messaging — Send messages to contacts and reply to active conversations
- Company Records — List companies, inspect profiles with user counts and custom data
- CRM Search — Search contacts and companies using Intercom's query syntax
- Admin Management — List all team members and their roles
How it works
1. Subscribe to this server
2. Enter your Intercom Access Token from the developer hub
3. Start managing customers from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Support Teams — manage conversations and reply to customers through AI
- Sales Teams — search leads, inspect company profiles, and track engagement
- Customer Success — monitor conversations and contact activity
Built-in capabilities (12)
Register a new contact
Start a new conversation
Get details for a contact
Get conversation history
List workspace admins
List Intercom contacts
List recent conversations
List custom attributes
List help center articles
List workspace segments
Reply to a conversation
Search contacts with filters
Why Cursor?
Cursor's Agent mode turns Intercom into an in-editor superpower. Ask Cursor to generate code using live data from Intercom 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
Intercom in Cursor
Intercom and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Intercom 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 Intercom in Cursor
The Intercom 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
Intercom for Cursor
Every tool call from Cursor to the Intercom MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for contacts and send messages through the AI agent?
Yes. Use search_contacts to find contacts by email, name, or custom attributes. Then use send_message to send a message to a specific contact, or reply to an active conversation thread.
Can I view full conversation histories?
Yes. list_conversations shows all conversations with status. Use get_conversation with a conversation ID to retrieve the full message thread including sender, timestamps, and content.
What type of Intercom token do I need?
You need an Access Token from a Private App in the Intercom Developer Hub. This provides scoped API access with Bearer authentication against api.intercom.io.
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.