Skip to main content
Glama
markmnl

fmsg-mcp

by markmnl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to fmsg-mcp

No user-submitted related servers found.

    Related Servers

    • agoradm-mcp

      shichuanqiong
      A
      license
      A
      quality
      B
      maintenance
      DM / IM for AI agents over the A2A 1.0 protocol — send and receive agent-to-agent DMs, manage friends and group threads, and rehydrate per-friend persistent memory with one-call wake context. 12 tools, pip install agoradm-mcp, stdio transport.
      12
      Apache 2.0

    • technocore-mcp

      0xgoodcrypto
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to read and write technocore.chat messages with a did:key identity, including end-to-end encrypted rooms, via 14 tools over stdio.
      14
      Apache 2.0

    • agentic-messaging-mcp

      ReferMore
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to send, receive, and discover contacts on the agentic message bus via native tools.
      5
      MIT

    • SwarmBridge

      Wersky
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns a shared GitHub repository into a message bus so that agents and their subagents on two different machines can converse in parallel: an issue is a thread, a comment is a reply, and closing it is an acknowledgement. Provides zero-dependency tools for sending addressed or broadcast messages, incrementally polling an inbox with a per-identity cursor, reading and replying within threads, and closing the loop with an ack.
      MIT

    • ChatRail MCP

      pedroantonnio
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI runtimes and tools drive a local WhatsApp session through an HTTP-backed stdio interface, supporting message sending, chat listing, unread counters, replies, and read-state management. It keeps the WhatsApp provider in a single process so integrations can automate messaging without starting a competing session.
      37 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

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: listing vs fetching vs threading vs delivery status, sending vs replying, adding recipients, reacting, and waiting. The few adjacent tools (list_messages/list_sent, get_message/get_thread, send_message/reply) are clearly differentiated by their descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (resolve_address, get_thread, add_recipients, wait_for_message). There are no mixed conventions, vague verbs, or inconsistent styles.

    Tool Count5/5

    14 tools is well-scoped for a messaging server: read/list, thread, delivery, reactions, sending, replying, recipient management, attachment handling, address resolution, and session info. Each tool covers a meaningful operation without redundant or filler tools.

    Completeness4/5

    Core messaging workflows are well covered: receive, read, thread, reply, send, react, add recipients, and delivery status. Minor gaps exist such as no explicit draft creation/update tool (though drafts appear in list_sent), no attachment upload, and no search or deletion, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources