Mattermost MCP Server

Created By
pveva year ago
Mattermost MCP server to enable Claude to interact with Mattermost Workspaces
Overview

What is Mattermost MCP Server?

Mattermost MCP Server is a tool designed to enable Claude and other MCP clients to interact with Mattermost workspaces through the Mattermost API.

How to use Mattermost MCP Server?

To use the Mattermost MCP Server, clone the repository, install dependencies, configure the server with your Mattermost credentials, build the server, and then run it. You can also trigger monitoring manually or through HTTP endpoints.

Key features of Mattermost MCP Server?

  • Topic monitoring system to track messages in specified channels.
  • Tools for managing channels and messages, including posting messages and adding reactions.
  • User management tools to retrieve user profiles and lists.
  • HTTP endpoints for remote control and monitoring.

Use cases of Mattermost MCP Server?

  1. Monitoring discussions on specific topics in Mattermost channels.
  2. Automating message posting and reactions based on certain triggers.
  3. Analyzing message statistics in channels for insights.

FAQ from Mattermost MCP Server?

  • Can I monitor multiple channels at once?

Yes! You can configure the server to monitor multiple channels for specific topics.

  • Is there a way to trigger monitoring manually?

Yes! You can trigger monitoring manually using provided scripts or HTTP endpoints.

  • What programming language is used for this project?

The Mattermost MCP Server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pvev
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago