Skip to main content
Glama
RelayMessenger

Relay MCP

by RelayMessenger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Relay MCP

No user-submitted related servers found.

    Related Servers

    • agenzax-mcp

      Agenzax
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.
      18
      303 npm
      MIT

    • telegram-user-mcp

      alexmakeev
      A
      license
      Not graded
      quality
      B
      maintenance
      Integrates Telegram user account with MCP, exposing operations like reading and sending messages, managing chats, and more via stdio or SSE transport.
      Apache 2.0

    • mcp-crm

      Saipranoy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to access a CRM over stdio, with Microsoft Entra device-code sign-in so queries run as the signed-in user, and tools to start/check login and search CRM accounts.
      2 npm
      ISC

    • crewmeister-api

      BelStark
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.
      Apache 2.0

    • WhatsApp MCP

      jaingxyz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to list, read, search, and send WhatsApp messages via a persistent WebSocket connection with local SQLite storage.
      35 npm
      AGPL 3.0
    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 16 tools

    Disambiguation4/5

    The tools are mostly organized by clear resource and action pairs, but relay_send_message and relay_send_message_to_chat overlap in purpose, and set_contact_card vs update_contact_card could cause initial confusion. The descriptions do clarify the differences, so an agent can still reliably choose the correct tool.

    Naming Consistency5/5

    All tools use the relay_ prefix and a consistent snake_case verb_noun pattern. Variations like relay_send_message_to_chat and relay_mark_chat_read are still predictable and follow the same naming logic as the rest of the set.

    Tool Count4/5

    Sixteen tools is slightly above the ideal 3-15 range, but each tool maps to a distinct messaging or contact-card function. The count feels justified for the domain rather than bloated.

    Completeness4/5

    The tool surface covers the core Relay messaging lifecycle: chats, messages, threads, reactions, typing, read state, and contact-card management. Notable absences like message editing/deletion or attachment sending appear intentional given the text-message focus, but they are still minor gaps for a broader messaging API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources