Skip to main content
Glama
conarti

yandex-messenger-mcp

by conarti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to yandex-messenger-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-max-messenger

      woyaxnini
      A
      license
      A
      quality
      F
      maintenance
      An MCP server for MAX Messenger (Russia's national messenger by VK) that enables AI clients to send and read messages, manage chats and members, send media, and more through 21 tools.
      21
      35 npm
      7
      -

    • Telegram MCP Server

      alexeyleshchenko
      A
      license
      A
      quality
      A
      maintenance
      MCP server that acts as a gateway to Telegram, providing AI-optimized tools for messaging, search, and chat management via MTProto. Supports multi-user authentication with QR login and HTTP/stdio transports.
      8
      2
      MIT

    • express-cli

      IH8E
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the eXpress corporate messenger, enabling AI agents to list chats, search contacts, send messages, and wait for incoming messages with end-to-end encryption.
      394 npm
      MIT

    • whatsapp-mcp

      moonslayers
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that controls WhatsApp Desktop via Chrome DevTools Protocol using the user's real session, enabling tools to list chats, read messages, search contacts, and send messages with simulated typing and rate limiting.
      13 npm
      1
      MIT

    • Yandex Webmaster MCP

      askads
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.
      20
      21 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

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    Each tool has a distinct operational purpose, and the descriptions carefully clarify boundaries (e.g. full reactions vs. embedded reaction summaries, history pagination vs. context window). However, the cluster of message-reading tools (get_history, get_message_context, get_thread, list_reactions) could still cause some misselection without close reading.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern: list_chats, send_message, delete_message, get_poll. Minor deviations like mark_read, vote_in_poll, and bare search break the strict pattern but are still predictable and readable.

    Tool Count4/5

    At 19 tools, the server is above the typical sweet spot but not bloated: each tool addresses a concrete messaging capability (chat listing, history, threads, reactions, polls, file handling, moderation). The breadth is justified by the messenger domain, though a few read variants could arguably be consolidated.

    Completeness4/5

    Core messaging lifecycles are covered: send, read, edit, delete, react, pin, search, poll voting, and attachment download. Notable gaps like creating chats, creating polls, forwarding messages, and sending voice/gallery media exist, but they are workable gaps for an assistant operating on existing conversations.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources