Skip to main content
Glama
BarredEwe

time-messenger-mcp-server

by BarredEwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to time-messenger-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-max-messenger

      woyaxnini
      F
      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
      113 npm
      10
      -

    • 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.
      83 npm
      MIT

    • herald

      ZenonEl
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that allows AI assistants to send formatted text, files, and updates to Telegram topics, and to capture incoming messages from work chats into a local inbox for retrieval.
      28
      AGPL 3.0

    • ya360-mcp

      cyxar4uk
      A
      license
      A
      quality
      A
      maintenance
      An unofficial MCP server that enables AI assistants to work with Yandex Tracker, Yandex Mail, and Yandex Calendar on the user's behalf, supporting reading, writing, and workflow automations such as meeting follow-ups, standups, and email-to-task creation.
      2
      1
      MIT

    • msteams-mcp

      hickeroar
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Microsoft Teams that lets AI assistants search, message, and manage chats, meetings, files, and contacts using your existing Teams browser login—no app approval or Azure AD registration needed.
      1,223 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.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a unique target resource and action (send, get, search, list, follow/unfollow, mark). The getters are clearly differentiated by resource type (channel messages, thread messages, thread info, channel info, team info, user info, unread counts). No two tools appear to perform the same operation.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern with underscores, using verbs like get, list, search, send, follow, unfollow, mark, and login. The choice of verb is intuitive (list for enumeration, get for specific resources, search for queries). No mixed casing or inconsistent styles.

    Tool Count4/5

    22 tools is slightly above the typical 3-15 range but is justified by the breadth of messaging domain (teams, channels, threads, users, messages, unread counts). Each tool addresses a distinct part of the workflow, so the count is appropriate for a comprehensive messaging integration.

    Completeness3/5

    The tool set covers reading/searching messages, sending messages, managing thread subscriptions, and checking unread counts. However, it lacks update/delete operations for messages and create/delete operations for channels/teams, which are notable gaps for a full lifecycle. Agents can work around this but may hit dead ends when needing to modify resources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources