Skip to main content
Glama
raoulbia-ai

MCP Server for Intercom

by raoulbia-ai
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to MCP Server for Intercom

No user-submitted related servers found.

    Related Servers

    • Nimbus Copiloto MCP Server

      ruben-salas20
      F
      license
      A
      quality
      B
      maintenance
      MCP server for the Nimbus helpdesk that enables an AI assistant to manage support tickets, search cases, escalate issues, send responses, and track SLA compliance.
      3
      -

    • freshservice-mcp

      mchluba
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.
      MIT

    • Claude Conversation Memory

      adamkwhite
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that provides searchable local storage for Claude conversation history, featuring automatic topic extraction and weekly insight summaries. It enables Claude to retrieve context from past sessions through full-text search and organized file storage.
      10
      3
      MIT

    • soporte-ti-mcp

      raulperez0798
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes: list_conversations retrieves all conversations in a date range, while the other three are specific searches (by customer for conversations/tickets, by status for tickets). However, search_conversations_by_customer and search_tickets_by_customer could be slightly confused since both target customers, but their descriptions clarify the resource difference (conversations vs. tickets).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: list_conversations, search_conversations_by_customer, search_tickets_by_customer, search_tickets_by_status. The naming is predictable and readable throughout the set.

    Tool Count3/5

    With only 4 tools, the set feels thin for an Intercom server, which typically handles a broader range of operations like creating/updating conversations, managing contacts, or sending messages. While the tools cover basic retrieval and search, the count is borderline low for the domain's potential scope.

    Completeness2/5

    The tool surface is significantly incomplete for an Intercom integration. It only provides search and list operations, missing essential CRUD actions like create_conversation, update_ticket, or delete operations. There are also gaps in managing other Intercom resources such as contacts, companies, or messages, which will limit agent capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources