Intercom
Connect Intercom to manage conversations, tickets, contacts, and companies, and publish help center articles and news.
You paste the Access Token that Intercom's Developer Hub issues for a private app installed on your workspace, plus the one-word data region (us, eu or au) that workspace is hosted in.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.intercom.io
- Rate limits
- Private apps get 10,000 API calls per minute per app and 25,000 per minute across the whole workspace, refilled in 10-second windows.
Before you begin
- An Intercom workspace on any plan. The Developer Hub is free.
- A teammate account that can create apps in that workspace (Owner or Admin).
- Knowing which region hosts your workspace: US, EU or Australia.
Get your credentials
Open the Intercom Developer Hub
Sign in to Intercom and go to app.intercom.com/a/apps/_/developer-hub. Click Your apps in the sidebar.
Your apps
Apps you have built on the Intercom platform.
| App | Workspace | Type | Status |
|---|---|---|---|
| Reporting syncCreated Mar 4, 2026 | Acme Support | Private | Installed |
| Billing lookupCreated Jan 9, 2026 | Acme Support | Private | Not installed |
Click New app to start a fresh one for PopMCP.
Create a private app for PopMCP
Click New app, type PopMCP in the name field, and pick your workspace from the Workspace dropdown. Click Create app.
Your apps
Apps you have built on the Intercom platform.
One app installs on one workspace. Create a second app for a second workspace.
Copy the Access Token
In the app sidebar open Configure → Authentication. Copy the value shown under Access Token.
Authentication
How this app proves who it is when it calls the Intercom API.
- App ID
- tc9x****
- Type
- Private
- Installed on
- Acme Support
The same token is repeated under Test and publish → Your workspaces.
Paste the token and region into PopMCP
Paste the token into Access token, then set Data region to us, eu or au to match your workspace. Leave the region blank for US.
Connect in PopMCP
Open your workspace, choose Intercom in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Access tokensecret | Intercom Developer Hub → Your apps → (create or open an app) → Authentication → Access token. The token carries the permissions set on that app. Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
| Data region (us, eu, or au)text | Where your Intercom workspace is hosted: us (default, api.intercom.io), eu (api.eu.intercom.io), or au (api.au.intercom.io). Tokens only work against their own region's host. |
PopMCP verifies the credential against Intercom immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Intercom connection flips to Connected in PopMCP and its tools appear. Listing recent conversations returns real records from that workspace.
Troubleshooting
401 Unauthorized on every call
Why: The token belongs to a workspace in a different data region than the one selected, or it was truncated when copied.
Fix: Re-copy the whole Access Token from Configure → Authentication, then set Data region to us, eu or au to match your workspace. Each region has its own host: api.intercom.io, api.eu.intercom.io, api.au.intercom.io.
403 Forbidden on some endpoints only
Why: The app does not hold the permission that endpoint requires.
Fix: Open the app in the Developer Hub, tick the missing read and write permissions, save, then reconnect in PopMCP.
No Access Token shown on the Authentication page
Why: The app was never installed on a workspace.
Fix: Go to Test and publish → Your workspaces and click Install app next to the workspace you want. The token then appears beside it.
The connection stopped working after someone clicked Regenerate token
Why: Regenerating issues a new Access Token and invalidates the old one.
Fix: Copy the new token from Configure → Authentication and update the PopMCP connection.