matrix-mcp
Related Servers
Alternatives to matrix-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA standalone MCP tool server that exposes Matrix chat operations as callable tools, enabling messaging, room management, user management, and ID resolution for MCP-compatible clients.168 npmMIT
- AlicenseAqualityAmaintenanceMCP Server for the Mattermost API, enabling Claude and other MCP clients to interact with Mattermost workspaces.1363 npm6MIT
- AlicenseNot gradedqualityCmaintenanceA safe-by-default MCP server that gives Claude access to your Proton Mail through Proton Mail Bridge's localhost IMAP/SMTP. Sending requires human approval and destructive operations are limited.29 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude to your Google Chat workspace, enabling search of messages, spaces, and DMs with automatic resolution of real display names.MIT
- AlicenseNot gradedqualityBmaintenanceStandalone Matrix MCPL server that connects Matrix rooms and DMs to an MCPL host as a first-class channel surface, enabling real-time messaging, threads, typing indicators, attachments, and rollback via MCPL tools.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that lets Claude read and send WhatsApp messages using a genuine WhatsApp Web client behind a code-enforced human-behavior middleware for safety.-
TDQS
Scored across 11 tools
Each tool targets a distinct resource+action: listing rooms vs. getting one room's info, browsing recent messages vs. full-text search, and sending message/file/reaction are clearly separated. No two tools overlap in a way that would cause misselection.
Every tool follows the same matrix_verb_noun snake_case pattern (list_joined_rooms, get_room_info, send_message, create_room, etc.). Verbs are consistent and predictable across the set.
11 tools is well-scoped for a Matrix client covering rooms, messaging, and search. Each tool earns its place without redundancy or bloat.
Coverage is strong for read/send workflows: list rooms, room info, members, read/send messages, files, reactions, mark read, create room, invite, search. Notable gaps remain for lifecycle operations like join/leave room and redact/delete messages.