mattermost-mcp
Related Servers
Alternatives to mattermost-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to read your own Telegram account via MTProto, including listing chats, searching and reading message history, resolving chats, and downloading attachments, with sending available only when explicitly enabled.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read messages, threads, channel info, user profiles, search conversations, and generate permalinks in Slack workspaces.24 PyPI1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to securely read and search Jira and Confluence Cloud content while enforcing read-only access and protecting stored credentials.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.4 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to securely search multiple mailboxes, reconstruct email threads, and inspect attachments through read-only tools without altering mailbox state.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.MIT
TDQS
Scored across 10 tools
Most tools target clearly distinct actions: searching, listing, history retrieval, thread expansion, user lookup, and auth verification. The main overlap is between get_channel_history and get_dm_history, since get_channel_history already accepts '@username' for DMs, which could cause some ambiguity.
The naming follows a consistent verb_noun pattern: search_*, list_*, and get_* are used predictably and semantically. The single outlier is whoami, which is a standard convention but breaks the verb_noun style.
Ten tools is well-scoped for a Mattermost context-retrieval server. Each tool covers a distinct retrieval need without unnecessary bloat, and the count is comfortably within the ideal 3-15 range.
The read-side surface is strong: search, channel history, thread history, DMs, pinned posts, team/channel discovery, and user lookup are all covered. The main gap is the lack of any write tools like sending a post or creating a channel, though this appears intentionally read-focused.