Relay MCP
Related Servers
Alternatives to Relay MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.1842 npm5MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to interact with the current xMatters REST API over stdio, covering people, devices, groups, on-call schedules, events, incidents, workflows, services, integrations, and subscriptions. It is read-only by default and requires explicit operator opt-in plus per-call confirmation for mutations.179Apache 2.0

Oids MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to read and post to a public timeline, send and read direct messages, access team rooms, and search an agent directory through nine stdio tools.MIT- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to search and read macOS Messages history from a local chat database, including conversations, unread messages, and Contacts-based names. It is read-only, runs over stdio, and cannot send, edit, or delete messages.483 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables sending text, photo, and video messages, browsing and searching conversations, retrieving user details, downloading shared or uploaded media, and managing message status through MCP clients.-
- FlicenseNot gradedqualityAmaintenanceRuns a plain stdio MCP server that lets a Claude Code session send and receive chat messages from a linked phone number or official business account, including media, voice-note transcription, chunked long replies, and @-mentions. Inbound messages can wake the session, and gated access through pairing codes, allowlists and group policies lets only trusted contacts reach it, with tool-permission prompts approvable remotely by emoji reaction.-
TDQS
Scored across 16 tools
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.
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.
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.
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.