From eb11bb94425b007be70e414330d74594e9d1620c Mon Sep 17 00:00:00 2001 From: "david.delagneau" Date: Wed, 20 May 2026 14:30:43 -0600 Subject: [PATCH] feat: update Mattermost integration documentation with MCP support guidelines and focused reader mode instructions --- agent-memory/integrations/communication-sources.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/agent-memory/integrations/communication-sources.md b/agent-memory/integrations/communication-sources.md index b13fc10..0a985cc 100644 --- a/agent-memory/integrations/communication-sources.md +++ b/agent-memory/integrations/communication-sources.md @@ -1,7 +1,7 @@ --- type: agent-integration status: active -updated: 2026-05-19 +updated: 2026-05-20 tags: - communication - evidence @@ -27,6 +27,8 @@ Mattermost is the current live communication connector. - Latest-message requests are read-first. The agent may identify a memory update candidate, but should not edit `project-knowledge/` from the latest-message command unless the user explicitly asks to promote the fact. - Standup generation is a separate required-refresh flow: it must fetch Mattermost before drafting, even though general prompts should not sync automatically. - Standup reads should use the focused reader mode, `scripts/mattermost-proxy/read-context.py --mode standup --today YYYY-MM-DD`, which reads date-bucketed previous-workday/today records and should use the active profile's configured `AIW_MATTERMOST_CONTEXT_CHANNELS` when available. Avoid loading broad mirror `latest.md` into standup prompts because it may include stale or unrelated channels and waste tokens. Keep project-specific channel names out of reusable connector code. +- If adding MCP support for Mattermost, treat it as a read-only query wrapper over the existing proxy mirror and `read-context.py`, not as a replacement for the capture/mirror pipeline. Keep the mirror's file layout as canonical raw evidence and expose only narrow tools such as latest, standup/date, channel, and thread reads with channel filters and limits. +- Do not build a write-capable Mattermost MCP or expose tokens, cookies, raw headers, or broad unfiltered raw dumps through MCP. MCP output should remain evidence for agent reasoning; promotion to `project-knowledge/` still follows normal memory rules. - If the proxy mirror is running, treat it as fresher than legacy `mattermost-latest.md` / generated JSONL. Do not ignore mirror evidence merely because a legacy sync command also ran. - Do not refresh Mattermost just because a prompt mentions a manager or stakeholder. - Treat document review, message polishing, translation, and "does this align with Jeff's expectations?" prompts as normal drafting tasks unless the user explicitly asks for the latest message or fresh Mattermost evidence.