Mattermost MCP Server

Mattermost MCP server to enable Claude to interact with Mattermost Workspaces

Local serverstdio

What is the Mattermost MCP server?

Connect Mattermost to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Mattermost MCP server to enable Claude to interact with Mattermost Workspaces. The mattermost mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • mattermost_list_channels — List public channels in the workspace
  • mattermost_get_channel_history — Get recent messages from a channel
  • mattermost_post_message — Post a new message to a channel
  • mattermost_reply_to_thread — Reply to a specific message thread
  • mattermost_add_reaction — Add an emoji reaction to a message
  • mattermost_get_thread_replies — Get all replies in a thread
  • mattermost_run_monitoring — Trigger the topic monitoring process immediately
  • mattermost_get_users — Get a list of users in the workspace
  • mattermost_get_user_profile — Get detailed profile information for a user

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mattermost's toolset — mattermost_list_channels, mattermost_get_channel_history, mattermost_post_message and 6 more — is a fair guide to whether it matches your workflow. It is maintained by pvev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mattermost's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mattermost.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
mattermost_list_channelsList public channels in the workspace
mattermost_get_channel_historyGet recent messages from a channel
mattermost_post_messagePost a new message to a channel
mattermost_reply_to_threadReply to a specific message thread
mattermost_add_reactionAdd an emoji reaction to a message
mattermost_get_thread_repliesGet all replies in a thread
mattermost_run_monitoringTrigger the topic monitoring process immediately
mattermost_get_usersGet a list of users in the workspace
mattermost_get_user_profileGet detailed profile information for a user

How to install the Mattermost MCP server

{
  "mcpServers": {
    "mattermost": {
      "command": "node",
      "args": [
        "/path/to/mattermost-mcp/build/index.js"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Mattermost to mattermost list channels.
  • Use Mattermost to mattermost get channel history.
  • Use Mattermost to mattermost post message.

Frequently asked questions

Node.js and npm are required. The server also needs a Mattermost personal access token and the workspace URL.