Mattermost MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATTERMOST_TOKEN | Yes | Your Mattermost authentication token | |
| MATTERMOST_TEAM_ID | Yes | The ID of the team to monitor | |
| MATTERMOST_CHANNELS | Yes | Comma-separated list of channel names to monitor | |
| MATTERMOST_ENDPOINT | Yes | Your Mattermost server URL |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mattermost_searchC | Fetch messages from Mattermost channels with optional search functionality |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching messages with optional search, leaving no room for confusion or misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'mattermost_search' follows a clear and descriptive pattern, but consistency cannot be assessed across a set of one.
A single tool is too few for a server named 'Mattermost MCP Server', which implies broader functionality for interacting with Mattermost (e.g., posting messages, managing channels, users). This minimal toolset feels thin and incomplete for the apparent scope.
The tool surface is severely incomplete for a Mattermost integration. While 'mattermost_search' covers fetching messages, there are obvious gaps such as creating messages, managing channels, handling users, or other core Mattermost operations, which will likely cause agent failures in typical workflows.