Skip to main content
Glama
rosquillas

Element MCP Server

by rosquillas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Element MCP Server

No user-submitted related servers found.

    Related Servers

    • openclaw-mcp

      elkimek
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code to communicate with an OpenClaw bot via Matrix, allowing you to send messages and read replies using natural language.
      297 npm
      MIT

    • telegram-slack-mcp

      nileshpatil6
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects Claude to your personal Telegram and Slack accounts, letting it read real DMs, groups, channels, unread messages, and search chats, with optional sending enabled by the user.
      98 npm
      MIT

    • Telegram MCP Server

      goncaloreis
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with your Telegram account, including reading messages, searching conversations, and sending messages.
      -

    • mcp-room

      unbywyd
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude chats to communicate across machines or sessions via shared encrypted rooms, with tools to create, join, send, read, wait, search, and delete room messages.
      11
      41 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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: list_rooms discovers available rooms, get_room_info provides room metadata, get_messages retrieves message history, and search_messages performs content searches. The descriptions clearly differentiate these functions, making tool selection unambiguous for an agent.

    Naming Consistency5/5

    All tools follow a perfect 'matrix_verb_noun' pattern with consistent snake_case throughout: matrix_list_rooms, matrix_get_room_info, matrix_get_messages, and matrix_search_messages. This predictable naming convention makes the tool set highly readable and organized.

    Tool Count4/5

    Four tools is reasonable for a Matrix server, covering core room discovery, metadata retrieval, message reading, and search functionality. However, the absence of write operations (like sending messages or creating rooms) makes the count feel slightly lean for a complete Matrix integration, though still well-scoped for read-only use cases.

    Completeness3/5

    The tool set provides excellent read-only coverage for rooms and messages, but lacks any write capabilities (e.g., send_message, create_room, join_room) or room management operations (e.g., leave_room, update_room_info). This creates notable gaps that could limit agent workflows, though the existing tools form a coherent read-only surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources