mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
Mattermost keeps the plugin's MCP server switch in the database rather than in a config file, so the role reads the plugin state, flips the server on, and reads back the personal access token through SQL, with reading and writing statements kept in separate directories. Take over the token the server issued instead of generating one: the value only exists once Mattermost has minted it, so it is persisted through sys-token-store rather than declared as a vault credential. Calls execute as the account the token belongs to, so the surface is bounded by that account's permissions rather than by an administrator role. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5 lines
56 B
YAML
5 lines
56 B
YAML
---
|
|
administrator:
|
|
tokens:
|
|
web-app-mattermost: ""
|