mattermost-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATTERMOST_URL | Yes | The URL of the Mattermost server (e.g., https://mattermost.company.com) | |
| MATTERMOST_TOKEN | Yes | Authentication token for Mattermost | |
| MATTERMOST_KEEPALIVE_MS | No | Keep-alive interval in milliseconds (default: 86400000) | 86400000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_threadB | Get Mattermost thread content by post ID |
| get_postA | Get single post content by ID |
| get_channel_postsC | Get posts from a channel |
| search_postsC | Search posts in team |
| list_channelsB | List channels in team |
| get_userA | Get user info by ID |
| send_messageC | Send message to channel |
| test_connectionA | Test Mattermost connection |
| get_unreadB | Get unread messages, threads and channels summary |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.