- Category: communication
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 15
- Triggers: 0
- Slug:
INTERCOM_MCP - Version: 20261018_00
Tools
Add internal note
Add internal note
Slug:
INTERCOM_MCP_ADD_INTERNAL_NOTEAdd an internal note to an Intercom conversation.Notes are internal-only and never visible to the end user, and this tool cannot send customer-visible replies. Adding a note never changes the assignee. If the conversation is snoozed and assigned to someone other than the authenticated teammate, adding a note will unsnooze (reopen) it. Use this to leave context, analysis, or a drafted response for a teammate to review in the Inbox.Required fields:- conversation_id: The conversation to add the note to. Accepts a raw numeric ID (e.g. ‘12345’), the prefixed form ‘conversation_12345’, or an Intercom Inbox URL. Regular conversations only — ticket IDs are not a supported input.
- body: The note content in HTML format (plain text is also accepted). Whitespace between block-level tags is converted into empty paragraphs and renders as unwanted blank space, so emit tags with no newlines or indentation between them.
Input Parameters
The note content in HTML format. Visible to teammates only — never sent to the customer.
Conversation ID. Accepts: raw ID (e.g. ‘12345’), prefixed ‘conversation_12345’, or an Intercom URL (e.g. ‘https://app.intercom.com/a/inbox/_/inbox/conversation/12345’). Regular conversations only — ticket IDs are not a supported input.
Create article
Create article
Slug:
INTERCOM_MCP_CREATE_ARTICLECreate a new article in the Intercom Help Center.Required fields:- title: The article title
- author_id: Numeric ID of the admin/teammate who authored the article
- description: A short summary of the article
- body: The article content in HTML format. Whitespace between block-level tags is converted into empty paragraphs and renders as unwanted blank space, so emit tags with no newlines or indentation between them. To create a deliberate blank line, insert a paragraph whose only content is .
- state: ‘published’ or ‘draft’ (defaults to draft if not specified)
- parent_id: Numeric ID of the parent collection or section
- parent_type: ‘collection’ or ‘section’ (required if parent_id is set)
Input Parameters
The article content in HTML format. Whitespace between block-level tags becomes empty paragraphs and renders as blank space, so emit no newlines or indentation between tags; for a deliberate blank line insert a paragraph whose only content is .
Fetch
Fetch
Slug:
INTERCOM_MCP_FETCHRetrieve detailed content for a specific Intercom resource by ID or URL.Use this tool when you have:- A prefixed ID from search results (e.g., ‘conversation_123456’, ‘contact_abc-def-123’, or ‘company_abc123’)
- An Intercom URL (e.g., ‘https://app.intercom.com/a/inbox/_/inbox/conversation/123456’)
- Full resource content with formatted text summary
- Metadata including state, timestamps, and associations
- Direct URL to view the resource in Intercom
- ‘get_conversation’ for conversation IDs
- ‘get_contact’ for contact UUIDs
- ‘get_company’ for company IDs
Input Parameters
ID of the resource to fetch. Preferred format: ‘conversation_<id>’, ‘contact_<id>’, or ‘company_<id>’. Also accepts Intercom URLs (e.g. ‘https://app.intercom.com/a/inbox/_/inbox/conversation/12345’, ‘https://app.intercom.com/a/apps/_/users/<uuid>’, or ‘https://app.intercom.com/a/apps/_/companies/<id>’). For raw IDs without a prefix, use ‘get_conversation’, ‘get_contact’, or ‘get_company’.
Get article
Get article
Slug:
INTERCOM_MCP_GET_ARTICLERetrieve complete details for a specific Intercom Help Center article.Returns:- Full article content including HTML body
- Metadata: title, description, author, state
- Timestamps: created_at, updated_at
- Parent collection/section information
- URL to view the article
- In structuredContent, the body field is { __untrusted_content: true, source, value, warning }
- In the text content, the body is fenced with <untrusted-article-body source=“article:<id>”>…</untrusted-article-body>
Input Parameters
Output
Get company
Get company
Slug:
INTERCOM_MCP_GET_COMPANYRetrieve complete details for a specific Intercom company.Returns:- Full company profile (name, company_id, plan, industry, size)
- Monthly spend and user count
- All custom_attributes with their values (critical for attribute auditing)
- Associated segments and tags
- Activity timestamps (remote_created_at, last_request_at)
- Raw company ID
- Prefixed ID (e.g., company_abc123def456)
- Intercom URL (e.g., https://app.intercom.com/a/apps/_/companies/abc123def456)
Input Parameters
Company ID. Accepts: raw ID, prefixed ‘company_<id>’, or an Intercom URL (e.g. ‘https://app.intercom.com/a/apps/_/companies/<id>’).
Get contact
Get contact
Slug:
INTERCOM_MCP_GET_CONTACTRetrieve complete details for a specific Intercom contact.Returns:- Full contact profile (name, email, phone, location)
- Role and signup information
- Custom attributes and metadata
- Last seen and activity timestamps
- Raw contact ID (UUID)
- Prefixed ID (e.g., contact_aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee)
- Intercom URL (e.g., https://app.intercom.com/a/apps/_/users/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee)
Input Parameters
Contact ID. Accepts: raw ID, prefixed ‘contact_<id>’, or an Intercom URL (e.g. ‘https://app.intercom.com/a/apps/_/users/<id>’).
Get conversation
Get conversation
Slug:
INTERCOM_MCP_GET_CONVERSATIONRetrieve complete details for a specific Intercom conversation.Returns:- Full conversation metadata (state, priority, timestamps)
- Complete message history with all conversation parts
- Associated contacts and tags
- Assignment and team information
- Raw conversation ID (e.g., 123456789)
- Prefixed ID (e.g., conversation_123456789)
- Intercom URL (e.g., https://app.intercom.com/a/inbox/_/inbox/conversation/123456789)
Input Parameters
Conversation ID. Accepts: raw ID (e.g. ‘12345’), prefixed ‘conversation_12345’, or an Intercom URL (e.g. ‘https://app.intercom.com/a/inbox/_/inbox/conversation/12345’).
List articles
List articles
Slug:
INTERCOM_MCP_LIST_ARTICLESList all articles in the Intercom Help Center.Returns a paginated list of articles with basic metadata.Pagination:- Uses page-based pagination (not cursor-based)
- Default: page 1, 25 articles per page
- Set ‘per_page’ (1–150) and ‘page’ to navigate results
- Response includes ‘pages’ object with total_pages and page count
Input Parameters
List companies
List companies
Slug:
INTERCOM_MCP_LIST_COMPANIESList Intercom companies with optional filters.Supports:- name: Find a company by exact name match (returns a single company)
- company_id: Find a company by its external company_id (returns a single company)
- tag_id: Filter companies by tag ID
- segment_id: Filter companies by segment ID
- Uses page-based pagination (not cursor-based)
- Default: page 1, 15 companies per page (max 60)
- Set ‘per_page’ (1-60) and ‘page’ to navigate results
- Response includes total_count and pages with total_pages
Input Parameters
Search
Search
Slug:
INTERCOM_MCP_SEARCHPurpose:- Search for resources in Intercom (conversations and contacts) using a unified query approach. For companies, use the list_companies tool.
- Note that only a subset of properties will be returned in search results.
- For complete details, use the Fetch tool with the returned IDs.
- MUST specify object_type:conversations OR object_type:contacts to indicate which API to call.
- Use specific field searches for precise filtering (e.g., email:john@example.com).
- Use the starting_after parameter for pagination when more results exist.
- Combine multiple search criteria with logical operators for complex queries.
- Returns results with id, title, text, and url for each match.
- IDs are prefixed with ‘conversation_’ or ‘contact_’ to indicate type.
- Use these IDs with the Fetch tool to get complete resource details. Note: When filtering by id/contact_ids in queries, provide raw IDs without prefixes. If you pass prefixed IDs to get_conversation/get_contact, they are accepted and normalized.
Input Parameters
Intercom Search Query DSL specification. MUST start with object_type:conversations or object_type:contacts to specify which API to call. Use tokens separated by spaces with key[:op]:value format. Examples: ‘object_type:contacts email:contains:“@example.com”’ for domain search, ‘object_type:conversations state:open created_at:gte:2024-01-01’ for recent open conversations. For companies, use the list_companies tool instead.
Search articles
Search articles
Slug:
INTERCOM_MCP_SEARCH_ARTICLESSearch for articles in the Intercom Help Center.Supports filtering by:- phrase: Free-text search across article title and body
- state: Filter by ‘published’ or ‘draft’
- help_center_id: Filter articles by a specific Help Center (numeric ID)
- highlight: When true, returns highlighted matching snippets
Input Parameters
Search contacts
Search contacts
Slug:
INTERCOM_MCP_SEARCH_CONTACTSSearch for Intercom contacts using multiple filter criteria.Supports filtering by:- IDs: Search for specific contact IDs
- Email/Domain: Filter by email address or domain
- Name/Phone: Search by contact name or phone number
- Custom Attributes: Filter by any custom data fields
- Results are paginated with up to 150 items per page (default 5)
- If more results exist, the response includes a ‘pages’ object with ‘pages.next.starting_after’ cursor
- To fetch the next page, make another request with the SAME search parameters plus the ‘starting_after’ value from the previous response
- Continue until ‘pages.next’ is not present in the response
Input Parameters
Pagination cursor for fetching the next page. Use the value from pages.next.starting_after in the previous response.
Search conversations
Search conversations
Slug:
INTERCOM_MCP_SEARCH_CONVERSATIONSSearch for Intercom conversations using multiple filter criteria.Supports filtering by:- IDs: Search for specific conversation IDs
- Source: Filter by source type (email, chat, etc.), author name/email
- State: Filter by conversation state (open, closed, snoozed)
- Assignment: Filter by team assignee ID or admin assignee ID
- Statistics: Filter by response times and assignment metrics
- AI Agent: Filter by Fin AI agent participation and resolution state
- Results are paginated with up to 150 items per page (default 5)
- If more results exist, the response includes a ‘pages’ object with ‘pages.next.starting_after’ cursor
- To fetch the next page, make another request with the SAME search parameters plus the ‘starting_after’ value from the previous response
- Continue until ‘pages.next’ is not present in the response
Input Parameters
Search conversations by source type. Accepted fields are conversation, email, facebook, instagram, phone_call, phone_switch, push, sms, twitter and whatsapp.
Pagination cursor for fetching the next page. Use the value from pages.next.starting_after in the previous response.
Filter by conversation rating requested timestamp. Supports operators <, >, =, !=, <=, and >=.
Submit mcp feedback
Submit mcp feedback
Slug:
INTERCOM_MCP_SUBMIT_MCP_FEEDBACKSubmit feedback about this Intercom MCP server to the Intercom team that builds it.After completing a task, briefly consider whether any capability on this server was missing, produced wrong or confusing results, or was harder to use than it should have been. If so, submit feedback so the team can improve the server. Also use this when the user explicitly asks to send feedback about this MCP server.Do NOT use this for:- Problems with OTHER MCP servers or their tools (Slack, Notion, GitHub, Google Drive, and so on) — even if this is the only feedback tool available in your session. This channel reaches only the team that builds the Intercom MCP server; they cannot act on another system’s bugs, and misfiled reports degrade the signal used to prioritize Intercom improvements. If another server’s tool failed, tell the user instead. Never file it here “so it is captured somewhere”.
- The Intercom product itself (the web app, the Inbox UI, Fin, pricing, billing) — this channel covers only this MCP server’s tool surface. Nothing filed here reaches the Intercom product teams.
- Support requests: nothing is created in the workspace, no ticket or conversation is opened, and nobody replies.
- Placeholder, test, duplicate, or “no feedback” submissions. If you have nothing concrete to report, do not call this tool at all.
- You could not accomplish something because no tool for it exists on this server (e.g. an Intercom API capability not yet exposed here)
- A tool on this server returned wrong, confusing, or incomplete results
- A workflow on this server required many tool calls or workarounds that could be streamlined
- A tool description on this server was misleading or its parameters were unclear
- summary: “Add a tool to reassign a conversation to another teammate” feedback: “There is no tool to update a conversation’s assignee. The user asked me to reassign 12 conversations to another teammate and I had to hand them back to the Intercom UI for each one.”
- summary: “Article search ignores the draft state filter” feedback: “search_articles with state:draft returned published articles too. Expected only drafts.”
- One submission per distinct issue per conversation. Skip transient errors that resolved on retry.
- Never include end-user personal data, conversation or message contents, or secrets.
Input Parameters
Who initiated this feedback: ‘user’ if the user asked you to send it or expressed the complaint themselves, ‘agent’ if you noticed the issue yourself.
A one-sentence headline for the ask or problem, phrased like a canonical feature-request title (e.g. ‘Add a tool to reply to a conversation as an internal note’). Plain English only — no tool names, IDs, URLs, markup, or error text. This field is clustered automatically across many workspaces, so prefer the most generic phrasing that is still accurate.
The type of feedback: ‘missing_capability’ when no tool exists for something the user needed, ‘bug’ for tool errors or wrong/unexpected results, ‘workflow_friction’ for flows that work but are overly complex, ‘other’ for anything else (including praise or general suggestions).
The full detail behind the summary. For missing capabilities: what capability is missing and why it would help. For bugs: what you did, what happened, and what you expected. For friction: what the user was trying to do and how the flow could be simpler.
string ("search_conversations" | "get_conversation" | "search_contacts" | "get_contact" | "list_companies" | "get_company" | "search" | "fetch" | "list_articles" | "search_articles" | "get_article" | "create_article" | "update_article" | "add_internal_note" | "submit_mcp_feedback")
The tool on this server the feedback is about. Only tools that exist on this server are accepted. If the capability you needed does not exist here, leave this out and describe it in requested_capability instead.
Briefly describe the wider task the user was trying to accomplish, in English. Omit the specific argument values you passed.
Update article
Update article
Slug:
INTERCOM_MCP_UPDATE_ARTICLEUpdate an existing article in the Intercom Help Center.Required:- id: The article ID to update
- title: Update the article title
- author_id: Change the author (numeric admin/teammate ID)
- description: Update the short summary
- body: Update the article content (HTML format). Whitespace between block-level tags is converted into empty paragraphs and renders as unwanted blank space, so emit tags with no newlines or indentation between them. To create a deliberate blank line, insert a paragraph whose only content is .
- state: Change to ‘published’ or ‘draft’. Omitting this field leaves the current publish state unchanged; it does not revert a published article to draft.
- parent_id: Move to a different collection or section (numeric ID)
- parent_type: ‘collection’ or ‘section’ (required if parent_id is set)
Input Parameters
Update the article content (HTML format). Whitespace between block-level tags becomes empty paragraphs and renders as blank space, so emit no newlines or indentation between tags; for a deliberate blank line insert a paragraph whose only content is .
Change to ‘published’ or ‘draft’. Omitting this field leaves the current publish state unchanged.