MCP Gateway · Cursor
Connect Intercom to Cursor
In-app text, error messages and onboarding flows should match what the Help Center tells customers. With Intercom connected to Cursor through the Speakeasy MCP Gateway, the agent can read Help Center articles while you edit the UI they describe. Cursor hooks ask Speakeasy to allow or deny every prompt and tool call, and fail closed.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Intercom MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Intercom call inspected and logged.
Before you start
What Intercom needs first
A user who can create and configure an OAuth app in the Intercom Developer Hub does the Intercom side of the setup.
- The workspace must be hosted in the US or EU. Australian-hosted workspaces are not supported.
- You need permission to create and configure an OAuth app for the workspace.
- Intercom does not name a required plan or administrator role.
In Intercom
- Identify the workspace region from its hostname.
- Create an app in the Developer Hub.
- Enable OAuth, add the Speakeasy redirect URL, and select read permissions.
- Copy the Client ID and Client secret.
Set up
Add Intercom to Cursor in 4 steps
- 01
Add Intercom from the catalog
An admin finds Intercom in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Intercom uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Intercom
Give teams the
mcp:connectscope on the Intercom server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Intercom to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Intercom from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Intercom needs its own OAuth grant, so each person connects it once. Until they do, Intercom calls fail while the rest of the gateway keeps working.
From then on, Intercom's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Intercom
Match UI copy to the Help Center
While you edit a settings screen, ask Cursor for the article that explains it and align the labels and hints with the wording customers already know.
Link errors to the right article
Cursor lists the Help Center's articles and picks the right one for each new error message, so the link you add in code points to real guidance.
Read feedback on the screen you're changing
Search recent chat conversations about a feature and read what customers found confusing in it, before you start redesigning the screen that causes the most questions.
Tools
13 tools
Each Intercom tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
search_conversations
Search for Intercom conversations using multiple filter criteria.
get_conversation
Retrieve complete details for a specific Intercom conversation.
search_contacts
Search for Intercom contacts using multiple filter criteria.
get_contact
Retrieve complete details for a specific Intercom contact.
list_companies
List Intercom companies with optional filters.
get_company
Retrieve complete details for a specific Intercom company.
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every Intercom call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Intercom tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Intercom can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Does every Intercom call from Cursor carry a user identity?
Can a team read Intercom conversations without editing Help Center articles?
How do Cursor users get Intercom?
Are Intercom calls from Cursor logged?
Connect more