Mattermost MCP Server
Related Servers
Alternatives to Mattermost MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude and other MCP clients to interact with Mattermost workspaces, providing channel management, messaging capabilities, and topic monitoring functionality.43-
- 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.-
- -licenseNot gradedqualityAmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm91,120MIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables Claude to interact with Mattermost instances, supporting post management, channel operations, user management, and reaction management.10 npm1-
- FlicenseAqualityDmaintenanceMCP server for Mattermost that enables AI assistants to read posts, search messages, send messages, and manage channels.9-
TDQS
Scored across 13 tools
Tools target distinct resources and actions: channels, messages, threads, reactions, users, and files. The only odd one is mattermost_run_monitoring, which is unclear in domain and could be confused for a generic system task, but otherwise boundaries are clear.
All tools use the mattermost_ prefix and snake_case verb_noun naming (get_post, edit_post, list_channels). Minor variation exists (reply_to_thread, run_monitoring), but the pattern is highly predictable.
13 tools cover the main Mattermost interaction areas without excessive duplication. Each tool has a clear role, and the count sits comfortably in the well-scoped 3–15 range.
Core messaging lifecycle is partially covered: create, read, update (edit) exist, but no delete_post or remove_reaction, and file upload/channel management are absent. Notable gaps may force workarounds for common chat operations.