# Intercom

Use an Intercom workspace hosted in the US or EU and an account authorized to access the intended workspace data. The server requests **Read and list users and companies**, **Read conversations**, and **Read and write articles**.

Sign in through [Intercom's sign-in page](https://app.intercom.com/admins/sign_in).

### Identify the workspace region
1. Before signing in, check the Intercom workspace URL you normally use:
   - `app.intercom.com` is **United States**.
   - `app.eu.intercom.com` is **Europe**.
   - `app.au.intercom.com` is **Australia**.
2. Open [Intercom's sign-in page](https://app.intercom.com/admins/sign_in).
3. Under **Your account region**, select the region that matches the workspace URL.
4. Sign in to the workspace.
5. If Intercom does not find the workspace:
   1. Reopen the sign-in page.
   2. Under **Your account region**, select the region that matches the workspace URL.
   3. Sign in again.
6. Open the intended Intercom workspace.
7. Inspect the hostname in the browser address bar.
8. If the hostname is `app.au.intercom.com`, stop. Intercom does not support the MCP server for Australian-hosted workspaces.
9. Record the values that match the hostname:
   - For `app.intercom.com`, record remote URL `https://mcp.intercom.com/mcp` and issuer URL `https://mcp.intercom.com`.
   - For `app.eu.intercom.com`, record remote URL `https://mcp.eu.intercom.com/mcp` and issuer URL `https://mcp.eu.intercom.com`.

<!-- screenshot: the Intercom sign-in page with Your account region expanded, showing United States, Europe, and Australia -->

### Add the server in Speakeasy
1. In the Speakeasy AI Control Plane sidebar, under **Connect**, select **Sources**.
2. Click **Add Source**.
3. Choose **Custom remote server**.
4. On **Add a custom remote MCP server**, paste the remote URL from [Identify the workspace region](#identify-workspace-region) into **Remote MCP server URL**.
5. Click **Add server**.

This creates the hosted MCP server and opens its **Overview** page.

<!-- screenshot: the Add Source menu and the Add a custom remote MCP server page with the matching Intercom remote URL -->

### Connect your credentials
1. From the server's **Overview**, open **Settings**.
2. Under **Authentication**, click **Configure Manually**.
3. In **Attach Remote Identity Provider**, enter the issuer URL from [Identify the workspace region](#identify-workspace-region) in **Issuer URL**.
4. Keep the auto-derived **Slug** unless your project naming policy requires a different value.
5. Keep **Display name (optional)** unless your project naming policy requires a different value.
6. Under **Endpoints**, click **Discover**.

This fills the regional authorization, token, and registration endpoints.

7. Under **Session Client**, keep **Client Type** set to **Dynamic Client Registration (DCR)**.
8. Keep **Token Endpoint Auth Method** at the discovered default `client_secret_basic`.
9. Leave **Scope (override)** empty.
10. Leave **Audience (optional)** empty.
11. Click **Attach Identity Provider**.

The Speakeasy AI Control Plane dynamically registers the OAuth client with Intercom. There is no **Client ID** or **Client Secret** to paste.

<!-- screenshot: Attach Remote Identity Provider after Discover, showing the regional issuer and endpoints with Client Type set to Dynamic Client Registration (DCR); no secret values are present -->

When a client initiates Intercom access, complete the on-screen browser prompts with the intended workspace account.

This guide covers setup only. For anything beyond it — billing, tool behavior, limits — see Intercom's MCP documentation at https://developers.intercom.com/docs/guides/mcp.