Intercom (quick connect)

Explore authentication, permissions and available actionsExact inputs, sign-in scopes, access limits and approval rules.

Intercom (quick connect) uses Intercom's own MCP server. There's nothing to make in Intercom first: you sign in and approve Roster, and it's connected.

It's the quick, limited way in. With it, a hire can:

• search and read conversations,
• look up contacts,
• add an internal note to a conversation, which only your team sees.

It can't:

• reply to customers,
• assign, close or snooze conversations,
• be held to some teams: a hire with access sees every conversation the server shows,
• connect a workspace hosted in Australia. It works for workspaces hosted in the US or Europe.

Which to pickCopy Anchor Link

• Intercom (quick connect), this page: to try Intercom with a hire in a minute, or when hires only need to read conversations and leave notes for your team.
• Intercom: when hires should reply to customers, assign, close or snooze, stay inside their teams, or your workspace is hosted in Australia. It takes a few minutes more: you make a private app in Intercom and paste its access token.

You can connect both, and give each hire the one its work needs.

Connect itCopy Anchor Link

1. Open Integrations → Tools → Add a tool, search for Intercom (quick connect) and choose it.
2. Click Connect Intercom (quick connect). Roster makes the connection and opens Intercom.
3. Sign in if Intercom asks, choose your workspace and click Allow (or Authorize). You're back in Roster, connected.
4. Click Test connection. Roster lists every tool Intercom's server offers, with whether it only reads or changes something. Untick any tool no hire should use, and click Save tools.

Which tools there are is up to Intercom's server. When it adds or changes tools, click Test again on the connection; until then hires keep the tools you saved.

Choose what each hire may doCopy Anchor Link

Connecting it gives it to no one. On a hire's Tools tab, click Give access on the connection:

• Read only: only the tools the server marks as read-only, or that you ticked as Changes nothing.
• Read and write: every tool you saved on the connection, internal notes included.
• Tools: if you like, only some of them for this hire.

On the connection, Ask before using starts at Tools that change things: every internal note waits for a person's approval in chat until you change it.

Personal dataCopy Anchor Link

Intercom holds personal data about your customers and what they wrote. Hires see what Intercom's tools return, shortened when it's very long; Roster doesn't mask emails or phone numbers here as the full Intercom connection does. Give access only to hires whose work needs it, and choose Read only where that's enough. Everything a hire does here is on its timecard.

Good to knowCopy Anchor Link

• Changes in Intercom don't wake hires on this connection. To have a hire check it regularly, give it a responsibility on a schedule, or use Intercom, which can watch conversations.
• If the sign-in expires or is revoked, hires are told plainly; click Reconnect on the connection.

Tools and permissions reference

This reference is built from the same definitions Roster uses to connect Intercom (quick connect) and give hires access. It updates with each release.

Authentication and requested permissions

The account or app you connect sets the outer limit. Each hire's access can narrow it further. Connecting a tool gives it to no hire until you give access on that hire's Tools tab.

MCP OAuth

The server supplies its authorization details and requested scopes when you connect. Review its consent screen.

No fixed permission list is declared for this connection. Review the sign-in consent screen, the account's roles, and the service's own documentation before connecting.

Connection fields

Intercom (quick connect) connection fields

Field	What to provide
OAuth client ID clientId Optional	Only if the server asks you to create an app by hand. Usually leave it empty: Roster registers itself.
OAuth client secret clientSecret Optional · sealed secret	Use the value for your account or connection.
Ask before using askFirst Optional	With “Tools that change things”, a hire's call to any tool here that changes something waits for a person's approval in chat, and runs exactly as asked once approved. New connections start there; choose the other option once you trust the hires with this connection. Each hire's Tools tab can also ask for single tools. Choices: Only tools a hire is set to ask about (never); Tools that change things (writes). Starts with: writes.

Per-hire limits

Read-only hires receive only actions that read. Read-and-write access also allows actions that change things, where the connection itself permits them. An empty resource allowlist usually means everything the connected account can reach; each field below explains its meaning.

Intercom (quick connect) per-hire limits

Field	What to provide
Tools tools Optional	Leave empty for every tool on this connection.

Actions

Actions come from the MCP server you connect, so there is no fixed action list to promise here.

Use Test connection to inspect the exact names, descriptions and read/write classifications; select the actions and Save tools. Retest when the service changes. A server's read-only labels are supplied by that server: review them before granting access.

Watches and incoming events

• No built-in watch is declared. Give a hire a scheduled responsibility if it should check this service regularly.
• No incoming webhook handler is declared for this integration.

Limits and troubleshooting

• Permission errors: check both the connected account's rights and the hire's resource and read/write limits.
• Expired or revoked access: reconnect or replace the key on the connection.
• Rate limits and unavailable services can interrupt work. The hire's timecard records the outcome.
• The action schema describes accepted inputs. It does not grant additional access or bypass approvals.

Service documentation · Integration source reference