Skip to main content
Glama
verygoodplugins

FreeScout MCP Server

by verygoodplugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FreeScout MCP Server

No user-submitted related servers found.

    Related Servers

    • Freshdesk MCP Server

      nikhilchintawar
      A
      license
      A
      quality
      D
      maintenance
      Enables fetching and searching Freshdesk tickets, including details like conversations, attachments, and custom fields, via natural language queries.
      3
      231 npm
      1
      MIT

    • Zendesk MCP Server

      SShadowS
      A
      license
      A
      quality
      A
      maintenance
      Enables AI-powered ticket analysis and comprehensive Zendesk API integration via the Model Context Protocol, supporting both API token (CLI) and OAuth 2.1 (web) authentication modes.
      55
      312 npm
      5
      MIT

    • NKS osTicket MCP

      nks-hub
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage osTicket support tickets including listing, searching, reading, creating, updating, replying, deleting, managing subtickets, and downloading attachments.
      14
      1
      MIT

    • Freshdesk MCP Server

      Sidd07Dev
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.
      19
      MIT

    • Zendesk MCP Server for Heroku

      dsouza-anush
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Zendesk Support for managing tickets, comments, and filtering via the Model Context Protocol. It allows LLMs to perform actions like creating, updating, and listing support tickets through natural language in a Heroku-native environment.
      -
    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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools map to single distinct actions, but get_ticket, analyze_ticket, and get_ticket_context all center on reading/understanding a single ticket. The get_ticket description's 'Fetch and analyze' wording blurs its boundary with analyze_ticket, so descriptions must be read closely to avoid misselection.

    Naming Consistency5/5

    All tools use the freescout_ prefix with a clear verb_noun structure: get_ticket, add_note, update_ticket, create_draft_reply, search_tickets, get_mailboxes. The verbs and nouns are consistent and predictable, with no mixed casing or irregular naming patterns.

    Tool Count5/5

    Eight tools is an appropriate size for a helpdesk assistant server. Each tool covers a distinct stage of the ticket workflow without ballooning into unnecessary operations or feeling too thin for the intended scope.

    Completeness4/5

    The set covers lookup, search, analysis, status/assignment updates, internal notes, context gathering, and draft replies, which is enough for common support ticket workflows. Obvious gaps like sending replies directly or deleting tickets are absent, but those are reasonable boundary choices for an assistant that drafts rather than sends.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources