MCP Intercom Server
Related Servers
Alternatives to MCP Intercom Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables to search, view, and interact with Intercom contacts and conversations, including sending customer-visible replies and internal notes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create and train support bots, manage knowledge sources, review conversations and leads, access analytics and usage, and retrieve install snippets via the Model Context Protocol.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to read a merchant's helpdesk data—tickets, conversations, contacts, companies, agents, and routing groups—through the Model Context Protocol while handling rate limits and returning partial results when necessary.MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural-language querying of structured data via Model Context Protocol, allowing AI agents to answer questions without SQL or API knowledge.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Intercom support workflows, including searching and updating contacts, handling conversations, assigning and closing tickets, and logging notes.-
- AlicenseNot gradedqualityDmaintenanceProvides a standardized interface for interacting with Rocketlane's tools and services through the Model Context Protocol, enabling unified API access.1MIT
TDQS
Scored across 2 tools
The two tools have distinct primary purposes: one fetches recent conversations by time window, while the other searches with multiple filters. However, there is some overlap since 'list-conversations-from-last-week' could be seen as a subset of what 'search-conversations' can do with a created_at filter, which might cause minor confusion.
Both tools use kebab-case and follow a verb-noun pattern (list-conversations, search-conversations), which is consistent. The addition of 'from-last-week' in the first tool name is descriptive but breaks the pure verb-noun convention slightly, though it remains readable.
With only 2 tools, the server feels under-scoped for an Intercom integration. It lacks essential operations like creating, updating, or replying to conversations, which are core to customer support workflows, making the toolset too thin for the apparent domain.
The server only provides read-only access to conversations, missing critical CRUD operations such as creating conversations, sending messages, updating conversation states, or managing users. This leaves significant gaps that will hinder agents from performing common Intercom tasks.