Skip to main content
Glama
Sign In
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FirstReply MCP Server

No user-submitted related servers found.

    Related Servers

    • libredesk-mcp

      metanmai
      A
      license
      C
      quality
      D
      maintenance
      MCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.
      54
      7 npm
      4
      MIT

    • gapify-mcp-server

      mh-zeynal
      A
      license
      B
      quality
      C
      maintenance
      Exposes the Gapify (Chatwoot-compatible) customer-support API as MCP tools, letting assistants list and search conversations and contacts, send replies, assign teams, apply labels, and resolve tickets in English or Persian. Write actions carry annotations for client confirmation, and a raw-request tool covers endpoints outside the generated set.
      118
      35 npm
      MIT

    • Freshdesk Agent Studio

      Shaambhavi58
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely list, retrieve, and search Freshdesk support tickets through typed read-only MCP tools. It supports API-key authentication, rate-limit handling, safe logging, and an offline fictional demo mode.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 84 tools

    Disambiguation4/5

    Tools generally target distinct resource-action pairs, and descriptions clarify overlaps like conversation_reply vs message_send. However, some pairs (conversation_thread vs conversation_get + conversation_messages, search vs knowledge_search) could cause hesitation. Overall mostly distinct.

    Naming Consistency5/5

    All tool names follow a consistent snake_case resource_action pattern (e.g., conversation_list, webhook_create, knowledge_source_sync). There are no mixed conventions, making the set predictable and easy to navigate.

    Tool Count1/5

    84 tools is an extreme mismatch for an MCP server, as the sheer volume will overwhelm an agent's context and decision-making. According to the calibration, 50+ tools merits the lowest score despite the platform's breadth.

    Completeness3/5

    Core workflows for conversations, contacts, classifications, templates, prompts, and webhooks have full CRUD. However, key lifecycle operations are missing for inboxes (no create/update/delete) and knowledge sources (no create/update/delete), creating notable dead ends for administrative tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources