
Shortcut: conversations involving a contact id (`contact_id` path-style filter on field `contact_ids`).
Generate MCP URLOverview: Shortcut: conversations involving a contact id (`contact_id` path-style filter on field `contact_ids`) through Intercom.
Benefits:
Common Use Cases:
With Adopt AI, your agents can tap into Intercom's full customer messaging capabilities. Here are five ways teams use the Intercom MCP integration:
1. Automated Conversation Routing & Triage
AI agents analyze incoming Intercom conversations, classify them by topic and urgency, and route them to the right support team or bot workflow.
2. Customer Health Scoring & Alerts
AI agents monitor Intercom engagement data to score customer health, flag at-risk accounts, and trigger proactive outreach from success teams.
3. Help Center & Knowledge Base Updates
AI agents analyze Intercom conversation trends to identify gaps in help center content and auto-draft new articles for common questions.
4. Support Metrics & SLA Monitoring
Automatically track Intercom response times, resolution rates, and SLA compliance, generating reports and alerts for support leadership.
5. Onboarding & Product Tour Automation
AI agents trigger personalized Intercom messages and product tours based on user behavior, lifecycle stage, and feature adoption patterns.

Loads a conversation including up to 500 recent parts. Optional `display_as=plaintext` returns plain text bodies.

Gets one team.

Updates a contact (email, name, custom_attributes, etc.) via `_rawBody`.

Shortcut: filter by `ticket_type_id` string, optional pagination.

Assigns or reassigns using `message_type: assignment`, admin actor, and `assignee_id` in `_rawBody` (not the same as PUT /conversations/{id}).

Removes a subscription association from a contact.

Retrieves one news item.

Returns the authenticated admin, embedded app (workspace), and seat flags. Call first to learn admin id for assignment and away-mode actions.

Retrieves a full contact record including related URLs for tags, notes, and companies.

Lists security and admin activity between UNIX timestamps. Query `created_at_after` is required; optional `created_at_before` bounds the window.

Updates ticket state, assignment, attributes, snooze, and visibility.

Permanently deletes an article by id.

Gets one newsfeed by id.

Lists metadata attributes, optionally filtered by `model` (contact, company, conversation).

Tracks a single user/lead event with name, timestamp, and flat metadata (max 10 keys). Returns 202 with empty body on success.

Creates a help center article. Send full article payload (title, body, parent collection, state, author_id, locales) in `_rawBody`.

Lists all newsfeeds.

Retrieves one help center configuration (URL, domain, display name).

Fetches one note by its id.

Shortcut: tickets assigned to admin `admin_assignee_id`, optional pagination.

Shortcut: substring match on contact `name` using operator `~`. For exact match use IC_SEARCH_CONTACTS with `=`.

Merges or converts a visitor into a lead/user; send visitor and target user payload in `_rawBody`.

Sends an admin-initiated in-app or email message; returns a Message object (conversation may not exist until reply).

Creates a ticket from `ticket_type_id`, contacts, and `ticket_attributes` in `_rawBody`.

Lists all workspace tags.

Creates a collection. Required fields such as `name` go in `_rawBody` per Intercom docs.

Deletes a company record by Intercom id.

Fetches a tag by id.

Adds a participant contact to a conversation; may create a lead if email is new.

Triggers workspace assignment rules for this conversation (deprecated in API 2.12; removed after 2026-12-31).

Full-text search across articles via query params (`phrase`, `state`, `help_center_id`, `highlight`). Prefer this over scanning IC_LIST_ARTICLES for keyword lookup.

Updates an attribute on a ticket type.

Lists all help centers in the workspace.

Creates a news item; include title, body, sender_id, labels, state in `_rawBody`.

Deletes a contact permanently by id.

Lists news feed items (draft/live) with pagination.

Applies an existing workspace tag to a conversation; body includes tag `id` and `admin_id`.

Tags many users/contacts at once: `_rawBody` follows `tag_multiple_users_request` (tag name plus `users`).

Loads a ticket by internal API `id` (not the human #ticket_id shown in the Inbox).

Shortcut: conversations where `open` is true, with optional `per_page` and `starting_after` pagination fields on the tool input.

Adds a custom attribute definition to a ticket type.

Updates a visitor identified by `user_id` or `id` inside `_rawBody`.

Removes a tag from companies: `_rawBody` follows `untag_company_request` (tag id plus company identifiers).

Lists published items for a specific newsfeed id.

Removes a tag from a ticket.

Creates a new tag: send `name` (and optional fields) in `_rawBody` per `create_or_update_tag_request` without an id.

Retrieves a visitor by `user_id` query parameter (required).

Updates an existing tag: include the tag `id` and changed fields in `_rawBody` (same `/tags` endpoint as create; not a PUT on `/tags/{id}` in API 2.10).

POST alternative to list companies with `page`, `per_page`, and `order` query params. Use when you need explicit sort order (asc/desc by last_request_at).

Retrieves one article including content and statistics.

Lists companies linked to a contact.

Creates or updates a company keyed by `company_id` in `_rawBody`. Companies appear only when at least one user is associated.

Adds a public reply, note, or comment to a conversation thread. Payload includes message_type, author, and body per API.

Shortcut: filter conversations by `priority` field (e.g. priority vs not_priority per workspace), optional pagination.

Merges a source contact into a destination. Send `from` and `into` contact ids in `_rawBody`.

Removes a tag from a conversation.

Tags a ticket; body includes tag `id` and acting `admin_id`.

Snoozes until `snoozed_until` UNIX timestamp using `message_type: snoozed` and `admin_id` in `_rawBody`.

Removes a contact participant from a conversation.

Gets a single company by Intercom object id (not the same as `company_id` string).

Lists teams for assignment routing.

Deletes a collection by id.

Starts a conversation from a contact; returns a user message with `conversation_id` when successful.

Creates a ticket type (name, description, icon, category) in `_rawBody`.

Removes a tag from a contact (path `id` is the tag id).

Shortcut: conversations in snoozed state, optional pagination fields.

Reopens a closed or snoozed conversation with `message_type: open` and `admin_id` in `_rawBody`.

Lists workspace segments.

Associates a company with a contact. Company payload goes in `_rawBody` (e.g. company_id).

Restores an archived contact.

Shortcut: equality filter on `role` (`user` or `lead`). Use IC_SEARCH_CONTACTS for compound filters.

Lists contacts attached to a company.

Shortcut: equality on ticket `state` (e.g. submitted, in_progress), optional pagination.

Starts a workspace message export job for a created_at range. Only one active export job allowed; check rate limits in docs.

Shortcut: tickets linked to a contact id (`contact_id` maps to searchable `contact_ids`).

Deletes a news item.

Advanced conversation search with nested `query` and `pagination` in `_rawBody`. Use IC_SEARCH_OPEN_CONVERSATIONS or IC_SEARCH_CONVERSATIONS_BY_ASSIGNEE for common single-filter cases.

Sets away mode and optional reassignment behavior for the given admin id.

Lists subscription types attached to a contact (opt-in and opt-out states).

Updates collection fields with `_rawBody`.

Primary structured contact search: send `query` (nested filters), optional `pagination` in `_rawBody`. Prefer IC_GET_CONTACT_BY_EMAIL (and related shortcuts) for single-field equality lookups.

Creates a new user or lead. Send identifiers and attributes in `_rawBody` per create_contact_request.

Shortcut: filter by `team_assignee_id` (string) plus optional `per_page` / `starting_after`.

Updates fields on an existing article. Supply changed fields in `_rawBody`.

Updates an existing company by Intercom id. Send mutable fields in `_rawBody`.

Lists ticket types including embedded attribute definitions.

Redacts a conversation part or eligible source message. Send identifiers in `_rawBody` per redact schema.

Fetches one admin by Intercom id. Use after listing admins when you need full detail.

Shortcut: closed conversations (`open` is false), optional pagination fields.

Shortcut: tickets where `open` is true, optional `per_page` / `starting_after`.

Shortcut: equality search on phone number string.

Creates a note on a contact; body typically includes `body` and admin attribution per API examples.

Searches tickets with structured `query` and pagination in `_rawBody`. There is no GET /tickets list in API 2.10—use this for filtered lists.

Scroll API for iterating all companies without deep paging limits. Pass `scroll_param` from the previous response; only one scroll per app.

Shortcut: find a contact by `external_id` (your app’s stable id).

Converts a conversation into a ticket; requires `ticket_type_id` in `_rawBody`.

Shortcut: equality search on email. Prefer IC_SEARCH_CONTACTS when you need compound filters.

Lists available subscription types (email/SMS consent categories).

Deletes a tag from the workspace.

Updates limited fields (e.g. `read` boolean). For close, snooze, assign, or open use IC_CLOSE_CONVERSATION / IC_SNOOZE_CONVERSATION / IC_ASSIGN_CONVERSATION / IC_OPEN_CONVERSATION on `/parts`.
Do I need my own developer credentials to use Intercom MCP with Adopt AI?
No, you can get started immediately using Adopt AI's built-in Intercom integration. For production use, we recommend configuring your own API credentials for greater control and security.
Can I connect Intercom with other apps through Adopt AI?
Yes! Adopt AI supports multi-app workflows, so your AI agents can seamlessly move data between Intercom and CRMs, spreadsheets, messaging platforms, and more.
Is Adopt AI secure?
Absolutely. Adopt AI is SOC 2 Type 2 certified and ISO/IEC 27001 compliant, and adheres to EU GDPR, CCPA, and HIPAA standards. All data is encrypted in transit and at rest, ensuring the confidentiality, integrity, and availability of your data. Learn more here.
What happens if the Intercom API changes?
Adopt AI maintains and updates all integrations automatically, so your agents always work with the latest API versions, no manual maintenance required.
Do I need coding skills to set up the Intercom integration?
Not at all. Adopt AI's zero-shot API discovery means your agents understand Intercom's schema on first contact. Setup takes minutes with no code required.
How do I set up custom Intercom MCP in Adopt AI?
For a step-by-step guide on creating and configuring your own Intercom API credentials with Adopt AI, see here.