mattermost-mcp
Related Servers
Alternatives to mattermost-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP Server for the Mattermost API, enabling Claude and other MCP clients to interact with Mattermost workspaces.969 npm3MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server for interacting with Mattermost workspaces, providing tools to manage channels, messages, threads, reactions, and user profiles via the Mattermost REST API.-
- AlicenseAqualityAmaintenanceMCP server for T-Bank's Time Messenger (Mattermost-based) that enables AI assistants to read and send messages, manage threads, search channels and users, and track unread messages.2212 npm7MIT
- FlicenseNot gradedqualityFmaintenanceAn MCP server that enables Claude and other MCP clients to interact with Mattermost workspaces, providing channel management, messaging capabilities, and topic monitoring functionality.42-
- FlicenseNot gradedqualityDmaintenanceMCP server for Rocket.Chat, enabling AI agents to interact with Rocket.Chat workspaces via tools like listing users, sending messages, and managing channels.2-
- AlicenseNot gradedqualityBmaintenanceMCP 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.688 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: thread, post, channel posts, search, channels, user, message, connection, and unread summary. Even get_thread and get_post are clearly differentiated by thread vs. single post.
All tool names follow a consistent verb_noun pattern (get_, list_, search_, send_, test_). No mixed conventions or vague verbs.
9 tools is well within the ideal 3-15 range. Each tool serves a clear purpose without redundancy or bloat.
The set covers reading, searching, listing, sending, and connection testing, but notably lacks update/delete operations for posts, channel creation, thread replies, and marking messages as read. These gaps are significant for a full Mattermost workflow but may be workable for read-centric use cases.