searchLABSCO SUMMARY
Read on conversations, write only on articles — the permission split matches where an agent should be trusted.
Customer conversations are a record; an agent should read them, not edit them. Help Centre articles are content; an agent drafting and updating those is exactly the useful case. Intercom's required scopes encode that distinction rather than leaving it to policy. Contact lookup accepting a custom attribute is the practical detail — most support questions start from an identifier that is not an email.
What it is
Intercom's own endpoint, with a separate EU address for EU-region accounts. Thirteen tools: a generic search-and-fetch pair plus specific ones for conversations, contacts, companies and Help Centre content.
What you get
- A DSL search and fetch pair for general retrieval
- Advanced conversation search, and reading one conversation in full
- Contact lookup by id, name, email, phone or custom attribute
- Company listing and detail
- Help Centre articles: list, search, read, create and update
Requirements
OAuth in the browser, or a bearer access token. The permissions needed are read on users and companies, read on conversations, and read-write on articles. Their SSE endpoint is deprecated.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Finding what a customer reported
Search conversations, then read the one that matters in full.
02
Identifying who is asking
Look up the contact by whatever identifier you have, including a custom attribute.
03
Turning a repeated question into an article
Search the Help Centre, then create or update the article.
04
Staying in the EU region
Connect the EU endpoint rather than the default one.
14 tools
Listed in project docs. Your client may show a different list.
fetchsearch_conversationsget_conversationsearch_contactsget_contactlist_companiesget_companylist_articlessearch_articlesget_articlecreate_articleupdate_articleadd_internal_noteBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth in the browser (recommended) or a bearer Intercom access token; EU data-region accounts use the EU endpoint
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.intercom.com/mcpRequirements
- OAuth in the browser (recommended) or a bearer Intercom access token; EU data-region accounts use the EU endpoint
