Catching up after leave
Back from a week off, an engineer asks what happened in #platform. Memtro reads the week's posts, pulls the two threads with the most replies and summarises what was decided, with permalinks.
Ask what was said in any Mattermost channel or thread you can see.
Connect Mattermost with your site URL and a personal access token and Memtro acts as you: it lists your teams and channels, reads recent messages in a channel or a whole thread with who said what, searches a team with Mattermost's own syntax, and looks people up. There is no hourly sync. When asked, and once an administrator has granted each action by name, it posts, replies, edits, reacts, pins and sends direct messages under your name, creates, renames and archives channels, and adds or removes members. Deleting a post removes it for everyone and cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mattermost tool, reads what it needs, and answers with the source cited.
These tools change something in Mattermost. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Mattermost is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What was said in #incidents yesterday?
Summarise the thread where Priya asked about the launch date
Search the Engineering team for 'rate limit' from @tom since 1 October
Post in #announcements that the office is closed on Friday
Create a private channel called acme-renewal and add @jsmith and @lwong
Back from a week off, an engineer asks what happened in #platform. Memtro reads the week's posts, pulls the two threads with the most replies and summarises what was decided, with permalinks.
Laura Wong asks Memtro to open a private channel for the Globex renewal, add the two account managers and post the renewal date. Memtro creates the channel under her name, adds both people, who are notified and can read it, and posts the wording she approved.
The teams that lean on Mattermost most, a question each of them asks, and what they connect beside it.
A record in Mattermost is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Ask a system admin to allow personal access tokens under System Console → Integrations → Integration Management (and, for a non-admin, under User Management → Users → Manage Roles)
In Mattermost open your profile picture → Profile → Security → Personal Access Tokens, create a token with a description and copy it: it is shown once. The token acts as you
In Memtro open Connections → Mattermost, paste the Mattermost URL (the site root, without /api/v4) and the Personal access token, and connect
Ask what was decided in a channel this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mattermost tools are the same everywhere.
Only when you ask, and only what it has been granted: post a message to a channel, or a reply in a thread, as the connected user; edit the text of one of the user's posts; delete a post (removed for everyone, with its thread when it is a root post); send a direct message to one person as the connected user; add or remove the user's emoji reaction on a post; pin or unpin a post in its channel; set a reminder about a post for the connected user; create a public or private channel in a team; rename a channel or change its purpose or header; archive a channel; add people to a channel, or remove one person from it. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Mattermost URL and personal access token. Ask a system admin to allow personal access tokens under System Console → Integrations → Integration Management (and, for a non-admin, under User Management → Users → Manage Roles).
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time