Read and send Slack messages, manage channels and threads.
- Home
- Top MCPs for Communication
- Mattermost
Mattermost
Self-hosted Slack alternative — read and post from an AI agent.
Quick answer
What it does
Connects to a Mattermost server and exposes channel + team enumeration, message posting and reading, and reaction/thread support.
Best for
- Self-hosted chat automation
- Data-residency-constrained agent flows
- Channel summarisation
- Bot-style replies
Not for
- Teams on Slack or MS Teams
- High-throughput marketing flows
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "mattermost": { "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export MATTERMOST_URL=https://chat.example.com # export MATTERMOST_TOKEN=your-personal-access-token claude mcp add mattermost -- npx -y @conarti/mattermost-mcpRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "mattermost": { "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "mattermost": { "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "mattermost": { "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "mattermost": { "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ], "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.mattermost] command = "npx" args = [ "-y", "@conarti/mattermost-mcp", ] env = { MATTERMOST_URL = "${MATTERMOST_URL}", MATTERMOST_TOKEN = "${MATTERMOST_TOKEN}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "mattermost": { "command": { "path": "npx", "args": [ "-y", "@conarti/mattermost-mcp" ] }, "env": { "MATTERMOST_URL": "${MATTERMOST_URL}", "MATTERMOST_TOKEN": "${MATTERMOST_TOKEN}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneMattermost doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
MATTERMOST_URL,MATTERMOST_TOKENin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Security & scope
- Access scope
- Network
- Sandbox
- Personal access token or bot token in env. Token inherits the issuing identity's permissions; use a dedicated bot account scoped to only the channels the agent should access.
- Gotchas
- Personal access tokens carry the issuing user's permissions — a privileged user's token is dangerous in agent loops.
- Mattermost admins can disable PAT issuance — coordinate with admin before relying on it.
- Self-hosted instances may use self-signed TLS certs; the MCP rejects them by default. Configure trust explicitly.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. communication work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-communication
Compare Mattermost MCP vs [Slack MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/mattermost - top-mcps.com listing for Slack
Install the Mattermost MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/mattermost (fetch https://top-mcps.com/mcp/mattermost.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (MATTERMOST_URL, MATTERMOST_TOKEN) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Communication MCPs
Other tools in the same category worth evaluating.
Compared with Mattermost
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Communication? See all Communication MCPs →
