MCP Gateway · Codex
Connect Intercom to Codex
Features gated by plan or account settings are easier to debug when you can see how a real customer is configured. Through the Speakeasy MCP Gateway, Codex can look up Intercom companies and contacts while it traces a bug through the code. Engineers sign in with your identity provider, and Speakeasy allows or denies each Codex tool call before it runs.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
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 Codex 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 Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Intercom from Codex
The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Intercom
Inspect a customer's account attributes
When a feature flag behaves oddly for one customer, Codex fetches the company's plan, user count and custom attributes so you can compare them with the gating logic.
Find the users behind a domain
Codex searches contacts by email domain to list everyone at an affected customer, along with when each was last seen, before you ship a targeted fix.
Tools
13 tools
Each Intercom tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex
The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Is Codex's Intercom activity sent to Speakeasy by default?
What does an Intercom admin set up before Codex can connect?
How do Codex users get Intercom?
Are Intercom calls from Codex logged?
Connect more