Ask what was said in a Rocket.Chat channel, or find a message by its words.
Connect Rocket.Chat with your workspace host, a personal access token and user id, and Memtro reads public channels, the rooms the connected user is in, recent messages and threads, message search, and profiles. Direct-message contents are never read. When you ask, and once an administrator has granted them by name, it can post, edit, pin and delete messages, react, save drafts that send nothing, create channels, groups and discussions, add or remove people, archive channels, set topics and announcements, and deactivate a user. Posting and adding people notify them, and deleting a message is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Rocket.Chat tool, reads what it needs, and answers with the source cited.
These tools change something in Rocket.Chat. 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 Rocket.Chat 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 decided in #ops yesterday?
Find the message where Dan mentioned the Northwind contract
What did people reply in the thread about the outage?
Post in #support that the fix is live
Save a draft in #customers about the outage, for me to send
The operations manager at BigCo is back from leave and asks what happened in #ops. Memtro reads the last week of channel messages and threads and summarises: a storage migration on Tuesday, one rollback, and Priya Nair owns the follow-up.
Priya Nair asks Memtro to open a private group for the Acme outage with Tom Reyes and Lena Park, and post the timeline there. Memtro creates the group, which adds and notifies both, then posts the message she approved as the connected user.
The teams that lean on Rocket.Chat most, a question each of them asks, and what they connect beside it.
A record in Rocket.Chat 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.
AgentMail
Fireflies.ai
SendGrid
Avoma
Missive
tl;dv
Grain
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
MailerSend
InfobipUse a dedicated bot or service user for Memtro, added only to the rooms it should read. Creating tokens needs the create-personal-access-tokens permission, and the token acts with every right of that user
In Rocket.Chat open avatar → Profile → Personal Access Tokens, name it Memtro, choose Ignore two-factor authentication, add, and copy the token and user id: both are shown once
In Connections → Rocket.Chat in Memtro type your Workspace host: your self-hosted domain, or <name>.rocket.chat on Rocket.Chat Cloud, with no https:// or path, then paste the Personal access token and the User id
Ask what was decided in #ops yesterday
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Rocket.Chat tools are the same everywhere.
Only when you ask, and only what it has been granted: post a message to one or several Rocket.Chat channels, groups or people (members are notified); edit a Rocket.Chat message (replaces its text); delete a Rocket.Chat message (cannot be undone); save the connected user's draft in a Rocket.Chat room (replaces any draft already there; nothing is sent); react to a Rocket.Chat message with an emoji, or remove the reaction; pin a Rocket.Chat message in its room (everyone in the room sees it); unpin a Rocket.Chat message; create a public Rocket.Chat channel (named members are added and notified); create a private Rocket.Chat group (named members are added and notified); open a Rocket.Chat direct message with one or more people (nothing is sent); add people to a Rocket.Chat channel (they are notified and can read its history); add people to a private Rocket.Chat group (they are notified and can read its history); remove a person from a Rocket.Chat channel; archive a Rocket.Chat channel (read-only for everyone); unarchive a Rocket.Chat channel; set a Rocket.Chat channel's topic; set a Rocket.Chat channel's announcement (shown to everyone in the channel); start a Rocket.Chat discussion in a room (members can see it); activate or deactivate a Rocket.Chat user (deactivating signs them out everywhere). 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.
Workspace host, personal access token and user id. Use a dedicated bot or service user for Memtro, added only to the rooms it should read. Creating tokens needs the create-personal-access-tokens permission, and the token acts with every right of that user.
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
