Claude + Mattermost: What the Integration Can (and Can't) Do in 2026
As of January 2026, Mattermost ships its own official MCP server — so Claude can securely read, search, and post to your workspace without a third-party plugin. That’s the headline: unlike most self-hosted tools, Mattermost built the connector itself. The other routes still exist and still matter — community MCP servers for Claude Desktop, and the plain Mattermost REST API v4 with a personal access token — but the official server is the one to reach for first.
Here’s each route, when to pick it, and what to use when you want Mattermost work that happens without you at the keyboard.
Route 1: The official Mattermost MCP server (best for most teams)
Mattermost released its official MCP server on January 16, 2026, delivered through the Mattermost Agents plugin (version 1.7.2 and higher) on Mattermost server v11.3. It’s available on all plans, self-hosted and cloud.
It works two ways. Internally, Mattermost Agents — Mattermost’s own built-in AI (formerly the Copilot / AI plugin) — can use it to summarize threads, search conversations, and draft posts inside the app. Externally, an admin enables the external MCP endpoint (the server’s /mcp path), and MCP-compatible clients like Claude connect over OAuth 2.0. When you authenticate, Claude inherits your exact Mattermost permissions — it can only touch the teams, channels, and content your own account can already reach. Per the Mattermost MCP docs, it can summarize long threads, run natural-language search across channels, pull context for incident response, draft messages, create posts, and set up new channels.
The catch: because it’s a self-hosted platform, this only exists once a server admin has upgraded to v11.3+, enabled Mattermost Agents, and switched on the external endpoint. On a locked-down corporate instance you don’t administer, that decision isn’t yours.
Route 2: A community MCP server + Claude Desktop
If you’re on an older Mattermost version, or you just want a local setup you fully control, a couple of open-source MCP servers predate the official one and still work well:
- pvev/mattermost-mcp (~39 stars, MIT, TypeScript) — lists channels, reads history, posts messages, replies in threads, adds reactions, looks up users, and includes a topic-monitoring notifier. It authenticates with a Mattermost personal access token and ships a ready
claude_desktop_config.jsonsnippet. - cloud-ru-tech/mcp-server-mattermost (~35 stars) — broader, ~38 operations across channels, messages, reactions, threads, users, teams, and files. It supports a static bot/personal token (the simple default), a client-token mode, and an OAuth proxy.
Both run as a local process wired into Claude Desktop via claude_desktop_config.json. You set MATTERMOST_URL and MATTERMOST_TOKEN (a bot or personal access token — more on those below), restart Claude Desktop, and the tools appear. Star counts are small; read the code before pointing one at a production workspace.
Route 3: The Mattermost REST API v4 directly
Every route above sits on top of the same foundation: the Mattermost REST API v4, served from /api/v4/. If you’re wiring your own script — or connecting through Claude Code — this is the honest base layer.
There are two auth paths. For read/write on behalf of an identity, create a bot account and generate a personal access token, then send it as a bearer header: curl -H 'Authorization: Bearer <token>' https://your-server/api/v4/users/me. For simple one-way “post this message to a channel” needs, an incoming webhook URL is even lighter — though webhooks only push messages in; they can’t read or search, so a bot-account token is the general-purpose choice.
Because Mattermost is open-source and self-hostable, the API is fully documented and stable — which is exactly why the community and official MCP servers could be built on it so quickly.
The limits that actually matter
- All three routes are session-bound. MCP tools — official or community — only run inside a Claude chat you start. Claude reads or posts when you ask it to, then stops.
- No triggers. Nothing here fires “when a message lands in #incidents.” There’s no listener watching your channels on your behalf.
- The local route needs Claude Desktop open. A community MCP server in Claude Desktop runs on your machine, so it’s gone the moment you quit the app. The official server lives on the Mattermost host, but Claude still only calls it during a live session you initiate.
- claude.ai on the web can’t reach a local setup. The browser app can connect to the official OAuth endpoint if your admin exposed it, but it will never see a desktop-only community server.
- You need admin cooperation for the official route. Enabling the external MCP endpoint is a server-admin action.
Claude + Mattermost is excellent for interactive work — “summarize the #outages thread,” “search last week’s release channel,” “draft an announcement post.” It’s not built for Mattermost work that needs to happen on a schedule or a trigger while you’re away.
If you want Mattermost work that runs on its own: Carly
Carly is an AI executive assistant that runs your Mattermost workflows on triggers and schedules — no chat session required.
- When a message mentions your bot in a channel, Carly triages it and posts a drafted reply or routes it to the right person.
- Every weekday at 8am, Carly summarizes overnight activity in your key channels and posts the digest — before anyone’s online.
- When a form or CRM event fires, Carly posts the alert to the right Mattermost channel automatically.
- No-code setup. You don’t write config files. Carly interviews you about what you want to happen, in plain English, and builds the workflow.
- Actually sends — Carly acts across Gmail and Outlook too, so a Mattermost trigger can fan out into email without you touching either.
- Connects to anything. Carly reaches Mattermost through your own Mattermost API key (paste it on the integrations page) — one of 200+ native integrations plus anything with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Capability | Claude + Mattermost | Carly |
|---|---|---|
| Read & search channels | Yes (official or community MCP) | Yes |
| Post & create channels in a session | Yes | Yes |
| Acts on triggers (new message, mention) | No | Yes |
| Runs on a schedule | No | Yes |
| Runs without a live chat open | No (session-bound) | Yes |
| Sends email (Gmail / Outlook) | No | Yes |
| No-code setup | No (config files / OAuth admin) | Yes |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best hands-on partner for reading and drafting inside your Mattermost workspace; Carly is the one that keeps those actions running on their own.
Frequently Asked Questions
Does Claude work with Mattermost?
Yes. Since January 2026, Mattermost ships an official MCP server (via the Mattermost Agents plugin on server v11.3+) that Claude connects to over OAuth. Community MCP servers and the REST API v4 are also solid routes.
Is there an official Mattermost MCP server?
Yes — Mattermost released it on January 16, 2026, through Mattermost Agents v1.7.2+. An admin enables the external MCP endpoint, and Claude connects with the same permissions as your own account.
Can claude.ai on the web access Mattermost?
It can reach the official OAuth MCP endpoint if your server admin has exposed it. It cannot see a community MCP server running locally in Claude Desktop.
Can Claude post to Mattermost automatically on a schedule?
No. Claude’s MCP tools only run inside a session you start — there’s no trigger or scheduler. For automatic, scheduled Mattermost posts, use an agent like Carly that runs on its own.
More: best Slack integrations · Claude + Slack integration · Claude connectors, explained · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
