mattermost-mcp
Related Servers
Alternatives to mattermost-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Mattermost workspaces for messaging, channel management, user operations, and file handling via the Model Context Protocol.MIT
- AlicenseAqualityCmaintenanceEnables AI coding tools to search and read a user's Mattermost channels and DMs using their own account, allowing AI to answer questions about team conversations with read-only access.10MIT
- AlicenseAqualityAmaintenanceLets AI assistants read, search, and post messages in Mattermost channels, manage threads, reactions, files, and users with 38 tools.391,589 PyPI49MIT
- FlicenseNot gradedqualityDmaintenanceThis server enables interaction with Mattermost workspaces to manage channels, messages, threads, and user profiles via the Mattermost REST API. It provides a comprehensive suite of tools for reading channel history, posting messages, and managing reactions within a trusted environment.-
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Mattermost workspaces to manage channels, messages, threads, reactions, and user profiles via the REST API. This server allows AI models to perform both read and write operations, such as posting messages and retrieving channel history, within a trusted environment.-
- AlicenseNot gradedqualityAmaintenanceEnables agents to read and write Slack through an ordinary browser session cookie, covering channel and thread history, full-text search over a local archive, and approved posting. It also supports an "agent forum" channel where agents of different people hand off tasks to each other, each keeping its own login and archive.MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource and retrieval path: single post (get_post), thread with replies (get_thread), channel history (get_channel_posts), DMs (get_direct_messages), mentions (get_mentions), and search (search_posts) are all clearly differentiated. Channel, user, and team lookups are similarly well-separated, leaving an agent little room for misselection.
Consistent snake_case with predictable verb_noun patterns: get_*, list_*, and search_* throughout. The only quirk, get_me, is an idiomatic convenience that still reads as a getter and doesn't break the pattern.
Fifteen tools is a natural fit for a chat workspace, spanning channels, users, teams, posts, search, and files. Every tool has a clear place and none look like filler.
Read coverage is thorough (posts, threads, channels, users, teams, files, search), but the surface is entirely read-only: there is no send_post, edit_post, delete_post, or channel-management operation. This is a notable gap for a messaging client, and get_me's write_enabled flag implies posting/editing tools are expected to exist.