Skip to main content
Glama
sewon-supernova

relation-mcp

by sewon-supernova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to relation-mcp

No user-submitted related servers found.

    Related Servers

    • Tiflux

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and operate a help desk and service desk through MCP over HTTP, including tickets, requester communications, internal notes, attachments, stage and SLA history, time entries, clients, requesters, desks, knowledge base, contracts, and billing/satisfaction reports.
      MIT

    • relay

      future-beat
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive Relay, an AI support-triage agent, by exposing tools for customer lookup, documentation search, ticket classification, reply, and escalation, with full guardrails and read-only mode option.
      MIT

    • Freshdesk MCP Server

      ArcaneSK
      A
      license
      A
      quality
      D
      maintenance
      Provides a standard MCP interface for Freshdesk helpdesk operations, including ticket lifecycle management, draft/send replies and notes, contact lookup, and agent/group discovery.
      14
      MIT

    • TicketDesk MCP

      bhargavlukka
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.
      MIT

    • zammad-mcp

      marcelofmatos
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to interact with Zammad ticketing system, enabling ticket search, creation, update, article addition, and user/organization/group queries via the Zammad API.
      3 npm
      MIT
    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.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tool purposes are mostly distinct, but `create_comment` and `create_record` both create internal notes with nearly identical functionality, which could cause confusion for an agent. The descriptions help differentiate slightly.

    Naming Consistency5/5

    All tool names follow a consistent `verb_noun` pattern in snake_case (e.g., `create_record`, `search_tickets`), making the naming predictable and unambiguous.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a ticket management system, covering the essential operations without being overly numerous or sparse.

    Completeness2/5

    Notable gaps exist: there is no `create_ticket` tool, so agents cannot initiate new tickets. Additionally, no delete or update operations for comments or records, and no customer creation/update, which limits the agent's ability to fully manage the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources