Ask what your Discourse forum is discussing, and who said what in a topic.
Connect Discourse with your site, an API key and a username, and Memtro reads latest topics, a topic's posts, forum search, categories, groups and member profiles. The key acts as its user and sees what that user can see, including private categories. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can start topics, reply, like and send private messages, which notify people and may email them, edit, close, move or delete posts and topics, manage categories and groups, and suspend, silence or deactivate a user.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Discourse tool, reads what it needs, and answers with the source cited.
These tools change something in Discourse. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Discourse, choosing the same kinds; the tab shows Discourse's own steps. Each event can start a job, with the event as its input. Discourse signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Discourse 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 are people asking about the new release this week?
Summarise the pricing feedback topic
Has anyone reported the export bug on the forum?
Which topics in Support have no replies yet?
Reply to the export bug topic saying a fix is planned for next week
The product manager at Acme asks what the community said about the new dashboard. Memtro searches the forum since the launch, reads the three busiest topics and summarises: praise for speed, two reports of a broken export, one feature request.
Priya Sharma asks Memtro to reply in the export bug topic that a fix is coming and then close it to new replies. Memtro posts the reply she approved as the connected user, people watching the topic are notified, and the topic is closed.
The teams that lean on Discourse most, a question each of them asks, and what they connect beside it.
A record in Discourse 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.
An administrator opens Discourse → Admin → Advanced → API keys → New API key, sets User level to Single user for a dedicated Memtro user, and Scope to Granular
Tick the topics, posts, search, categories and users read scopes, plus topics write and posts edit and delete only if Memtro may post. Save and copy the key: it is shown once
In Connections → Discourse in Memtro type your Site address with no https:// or path: a public DNS name with a publicly trusted certificate, then the API key and the Username it acts as
Ask what people asked about the new release this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Discourse tools are the same everywhere.
Only when you ask, and only what it has been granted: start a new topic in Discourse (watchers of the category are notified); reply to a Discourse topic (people watching the topic or mentioned are notified); send a Discourse private message (the recipients are notified, and emailed if they have that on); edit a Discourse post (replaces its text; the previous version stays in the post's revision history); delete a Discourse post (deleting a topic's first post deletes the topic; staff can restore it unless destroyed permanently); close, open, pin, unpin, archive, unarchive, list or unlist a Discourse topic; retitle a Discourse topic or move it to another category; delete a Discourse topic (staff can restore it); like a Discourse post (the author is notified); invite a forum member to a Discourse topic (they are notified); create a Discourse category (open to everyone); rename or recolour a Discourse category; add members to a Discourse group (changes what they can see and do); remove members from a Discourse group; suspend a Discourse user until a date (they cannot sign in); silence a Discourse user until a date (they cannot post); deactivate a Discourse user's account. 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.
Site, API key and Username. An administrator opens Discourse → Admin → Advanced → API keys → New API key, sets User level to Single user for a dedicated Memtro user, and Scope to Granular.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Discourse, choosing the same kinds; the tab shows Discourse's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
