mattermost-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATTERMOST_URL | Yes | Required. The original base URL of the Mattermost site. Do not include /api/v4, other paths, credentials, or query parameters. Production sites must use HTTPS; HTTP is only allowed for loopback local testing. | |
| MATTERMOST_MCP_DATA_DIR | No | Optional. Overrides the root directory used to store credentials. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mattermost_loginB | 建立一次性登入配對並回傳 npx 登入指令。MCP 在遠端時指定 sshTarget，讓本機 Login Helper 透過 SSH 交接 Session Token；同機則可省略。登入提供者由 Mattermost 站台設定決定。 |
| mattermost_auth_statusA | 驗證已保存的 Mattermost Session Token；不回傳 Token 本身。 |
| mattermost_get_current_userB | 取得目前登入的 Mattermost 使用者。 |
| mattermost_list_teamsB | 列出目前使用者可存取的 Mattermost teams。 |
| mattermost_list_channelsC | 列出指定 team 的 Mattermost channels。 |
| mattermost_search_postsC | 搜尋目前使用者有權限看到的 Mattermost posts。 |
| mattermost_get_channelB | 以頻道 ID 查詢頻道名稱、類型及封存狀態。唯讀操作。 |
| mattermost_get_postB | 取得單則訊息，包含 channel_id 及討論串 root_id。唯讀操作。 |
| mattermost_get_threadC | 取得指定訊息所屬的討論串及回覆。唯讀操作。 |
| mattermost_create_postA | 以目前登入者身分發送訊息。內容必須是 TL;DR：最多 5 行、每行最多 50 字；非唯讀，須有使用者授權；逾時不得直接重送。 |
| mattermost_reply_to_threadA | 以 TL;DR 回覆討論串：最多 5 行、每行最多 50 字。postId 可為根訊息或既有回覆，會自動找出 root_id 並檢查頻道歸屬；非唯讀，須有使用者授權。 |
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 11 tools
Each tool targets a distinct resource or action: login/status, current user, teams, channels, and posts are cleanly separated. get_post, get_thread, and search_posts are differentiated by scope, and create_post vs reply_to_thread is clear.
All tools share the mattermost_ prefix and snake_case, and most follow a verb_noun pattern such as get_channel, list_teams, and create_post. mattermost_login and mattermost_auth_status deviate slightly from strict verb_noun but remain readable and consistent with the set.
Eleven tools is well-scoped for a Mattermost integration, covering authentication, discovery, reading, and posting without obvious bloat. Each tool appears to earn its place.
Core read paths and posting/reply operations exist, but there is no channel history or recent-posts listing beyond search, and no update/delete post or channel management operations. These are notable gaps for common chat workflows.