Mattermost MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATTERMOST_URL | Yes | Mattermost API URL (e.g., https://mattermost.example.com/api/v4) | |
| MATTERMOST_TOKEN | Yes | Mattermost personal access token | |
| MATTERMOST_TEAM_ID | Yes | Mattermost team ID |
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 |
|---|---|
| mattermost_list_channelsA | List channels in the Mattermost workspace. By default lists public team channels. Set include_private=true to get all channels including private channels and direct messages (DMs). |
| mattermost_get_channel_historyA | Get messages from a Mattermost channel. By default returns ALL messages. Use limit parameter to restrict the number of messages. |
| mattermost_post_messageC | Post a new message to a Mattermost channel |
| mattermost_reply_to_threadB | Reply to a specific message thread in Mattermost |
| mattermost_add_reactionB | Add a reaction emoji to a message |
| mattermost_get_thread_repliesA | Get all replies in a message thread |
| mattermost_get_postB | Get a single message by its ID, including edit time and attachments |
| mattermost_edit_postA | Edit the text of an existing message. Mattermost marks an edited post as "Edited" for everyone in the channel. Only the post author or a user with permission to edit others' posts can edit it. |
| mattermost_get_file_infoA | Get metadata of a file attached to a Mattermost post: name, extension, size, MIME type, image width and height, post ID. File IDs come from file_ids and files in channel history and thread replies. |
| mattermost_download_fileA | Download a file attached to a Mattermost post to the local disk and return its absolute path and metadata. Without output_path the file is saved to the system temporary directory as mattermost-mcp/{file_id}_{name}. An existing file at the target path is overwritten. With inline=true a PNG, JPEG, GIF or WebP image up to 1 MB is also returned as image content; for other types or larger files the response explains why inline was skipped. |
| mattermost_get_usersB | Get a list of users in the Mattermost workspace with pagination |
| mattermost_get_user_profileB | Get detailed profile information for a specific user |
| mattermost_run_monitoringC | Run the topic monitoring process immediately |
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 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.