Skip to main content
Glama
future-beat

relay

by future-beat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to relay

No user-submitted related servers found.

    Related Servers

    • support-agent-mcp

      Kartz82
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes order status lookup and knowledge base search tools from the Support Agent AI over MCP, enabling MCP clients to handle customer support queries with grounded, citation-backed answers.
      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
    • Teletype MCP Server by Teletype-App

      Teletype MCP Serverofficial

      Teletype-App
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to find and read customer conversations, look up profiles, send replies, manage workspace metadata, and handle daily support workflows. It also supports triage, drafting, escalation, and handover tasks through MCP tools, prompts, and resources.
      320 npm
      1
      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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool performs a distinct action—lookup, search, categorize, reply, escalate, create, list—with no functional overlap. The descriptions explicitly differentiate when to use send_reply vs. create_escalation despite both ending the ticket.

    Naming Consistency5/5

    All seven tools follow a consistent verb_noun pattern in lowercase snake_case (lookup_customer, search_docs, set_category, send_reply, create_escalation, create_ticket, list_open_tickets). There is no mixing of conventions or stray verbs.

    Tool Count5/5

    Seven tools is well-scoped for a support-ticket agent: each tool maps to one step in the workflow without redundancy or bloat. The count feels intentional rather than padded.

    Completeness4/5

    The set covers the full support workflow—customer lookup, docs grounding, categorization, resolution, escalation, ticket creation, and listing. Minor gaps like a dedicated get_ticket or internal note action exist, but they are not required for the core automated support loop.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources