Attio MCP
OFFICIAL SERVERAttio's hosted MCP server for reading and editing records, lists, notes and tasks in an Attio workspace
Intercom's hosted MCP endpoint for searching conversations, contacts, companies and Help Center articles
Official · Intercom Remote (hosted) · Streamable HTTP CRM and sales
Opens the app, which asks before it adds the server.
https://mcp.intercom.com/mcpclaude mcp add --transport http intercom https://mcp.intercom.com/mcp{
"mcpServers": {
"intercom": {
"url": "https://mcp.intercom.com/mcp"
}
}
}{
"servers": {
"intercom": {
"type": "http",
"url": "https://mcp.intercom.com/mcp"
}
}
}Intercom runs this MCP server itself, on its own infrastructure. Nothing is installed: a client connects to the hosted address, the user signs in to their Intercom workspace, and the assistant gets tools for that workspace's data. Mostly it reads. It can search and open conversations and contacts with a small query language (for example object_type:conversations state:open), list and open companies, and list, search and read Help Center articles. A few tools change things: they create and edit articles and add internal notes to conversations.
The GitHub repository holds only a README and logos, and that README is out of date. It lists 6 read-only tools and says only US workspaces are supported. Intercom's developer guide now lists 14 tools, three of them writing ones (create_article, update_article, add_internal_note). It also documents a separate EU endpoint at https://mcp.eu.intercom.com/mcp, where requests stay in the EU. AU-hosted workspaces are not supported yet.
It suits support and product teams who want an assistant to look up customer history, read conversation threads or draft Help Center content without leaving their AI tool. The sign-in metadata at https://mcp.intercom.com/.well-known/oauth-protected-resource names two scopes, mcp and operator, and accepts bearer tokens only in the header.
An Intercom workspace hosted in the US or EU (AU is not supported) and an MCP client that can reach a remote Streamable HTTP server and sign in with OAuth. You can also use an Intercom access token with the scopes it needs: read users and companies, read conversations, write conversations (for notes), and read and write articles. On Claude Team or Enterprise, an org Owner adds the connector. If a client only speaks stdio, the docs bridge it with npx mcp-remote, which needs Node.js.
It cannot send customer-visible replies. add_internal_note writes notes only teammates see, signs them as the admin who authorised the connection, rejects ticket IDs, and reopens a snoozed conversation assigned to someone else. search returns 5 results by default and up to 150 per page. list_companies returns 15 by default, up to 60. There are no ticket, tag-management or user-deletion tools. The /sse endpoint is deprecated. Each region has its own endpoint, and connecting to the wrong one fails after consent. Custom clients with non-localhost redirect URIs need an allowlist entry from Intercom support. The GitHub README is outdated (6 tools, US only).
Teams already on Intercom who want an assistant to read support conversations, contacts, companies and Help Center articles. It is Intercom's own, hosted and signed in with OAuth, so there is nothing to run or update. Three tools write: they create and edit articles and add internal notes. If you want strictly read-only access, give a bearer token without the write scopes. If you need to send customer replies, manage tickets or work in an AU workspace, this server does not cover it.
searchfetchsearch_conversationsget_conversationsearch_contactsget_contactlist_companiesget_companylist_articlessearch_articlesget_articlecreate_articleupdate_articleadd_internal_note