mattermost-mcp-server

What is mattermost-mcp-server?

It is a Model Context Protocol (MCP) server that connects to Mattermost API endpoints to retrieve and process information. It uses secure, token-based authentication and makes Mattermost data available through standard MCP transports. It is designed for developers and teams who want to integrate Mattermost messaging with AI assistants or other MCP-compatible tools.

How to use mattermost-mcp-server?

Clone the repository, install dependencies, set required environment variables (MATTERMOST_ENDPOINT, MATTERMOST_TOKEN, MATTERMOST_TEAM, MATTERMOST_CHANNELS), then build and run with one of three transport modes: stdio, sse, or http-stream. Example: npx mcp-server-mattermost --transport stdio.

Key features of mattermost-mcp-server

• Secure, token-based connection to Mattermost API
• Supports stdio, sse, and http-stream transport modes
• Search for messages across multiple Mattermost channels
• Customizable default channels and message fetch limits
• Works with Claude Desktop via simple configuration

Use cases of mattermost-mcp-server

• Enable an AI assistant to search and retrieve Mattermost messages
• Integrate Mattermost data into MCP-compatible client applications
• Monitor team channels and extract information programmatically
• Automate workflows that require reading Mattermost conversations
• Build custom bots or tools that interact with Mattermost through MCP

FAQ from mattermost-mcp-server

What does mattermost-mcp-server do?

It acts as a bridge between Mattermost and the Model Context Protocol, allowing MCP clients (like AI assistants) to search and retrieve messages from Mattermost channels.

What are the runtime requirements?

Node.js version 22 or higher and npm version 10 or higher are required.

Where does the data live?

All data remains on your Mattermost server; the MCP server only accesses it via API calls and does not store any data locally.

What transport modes are supported?

The server supports three transport modes: stdio (default), sse, and http-stream.

How is authentication handled?

Authentication uses a token-based approach: you provide a Mattermost personal access token via the MATTERMOST_TOKEN environment variable. All API requests are authenticated with this token.