Mattermost is automatable through its API

Mattermost is automatable today through its REST API. The quick-start shows POST /api/v4/users/login with login_id and password, and the session token comes back in the Token response header. Later calls send Authorization Bearer. The same quick-start says the token placeholder is a personal access token. Personal access tokens do not expire, an admin must enable them, and they carry that user's permissions. The API reference indexes users, teams, channels, posts, files, and search. Mattermost also ships an official MCP server in the Agents plugin. The embedded server is always on. Read tools are available on every plan. Tools that change state, and the optional HTTP endpoint for external clients, require Enterprise or above. That endpoint stays off until Enable Mattermost MCP Server (HTTP) is turned on. It is then at /plugins/mattermost-ai/mcp-server/mcp and accepts OAuth or a personal access token. The January 2026 announcement tells external clients to use a shorter /mcp path and says Agents v1.7.2 is on all plans. The current admin guide is the tighter source for the path and the license gates. mmctl is the official admin CLI. It can print JSON and can log in with an access token or a password file. The opened page lists it for Entry, Professional, Enterprise, and Enterprise Advanced. Team Edition is a free MIT self-hosted server. Enterprise Edition can run free as Entry. Paid subscriptions and Mattermost Cloud are also documented, so deployment is hybrid. Incoming webhooks are documented. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 8. The MCP server scores 6 because external clients and writes are plan-gated. mmctl scores 6 because it is the admin tool. The API is the best path.

Best path today: api · Overall automatability: 8/10