> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Intercom

> Give the Sazabi agent tools to read support conversations, contacts, and help center content from your Intercom workspace.

[All Intercom integration capabilities](https://docs.sazabi.com/catalogs/integrations/intercom)

## About

Intercom is an MCP connector that gives the Sazabi agent tools to read support conversations, contacts, and help center content. Intercom ships an official hosted MCP server at `https://mcp.intercom.com/mcp` over Streamable HTTP. Sazabi authenticates using an Intercom API access token, stored securely and sent as `Authorization: Bearer <token>`. This connector currently supports US-hosted Intercom workspaces only.

**What the agent can do:**

* Search and read Intercom support conversations and tickets
* Look up contacts, leads, and companies
* Retrieve help center articles and collections
* Surface support context alongside the rest of an investigation

## Prerequisites

* A US-hosted Intercom workspace (Intercom's hosted MCP currently supports US-hosted workspaces only)
* An Intercom app with an API access token

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Intercom in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Add your key

In Intercom, go to **Settings > Integrations > Developer Hub**, open or create an app for your workspace, and copy the access token from its **Authentication** section. Sazabi sends it as `Authorization: Bearer <token>` to Intercom's hosted MCP endpoint. Paste the raw token into Sazabi — Sazabi adds the `Bearer` prefix.

## Set up with the CLI

Intercom authenticates with an Intercom API access token. With the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) installed and authenticated (see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)), connect it in one command, passing the credential as a header:

```bash theme={"system"}
sazabi mcp-connectors connect intercom --header "Authorization=Bearer <access-token>"
```

The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use `NAME=@<file>` to read a value from a file, or `--header-file <file.json>` for a JSON object of header names and values. To rotate the stored credentials later, use `sazabi mcp-connectors update-credentials <connection-id>`; find the connection ID with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized (OAuth) or the key/header is correct (token auth).

## Troubleshooting

**No tools discovered** — Confirm the access token is valid and the Intercom app has the permissions you need; re-enter the token from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Connection shows needs attention** — The authorization or key may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.