Finding the policy
A new starter at Brightwave Ltd asks how to claim travel expenses. Memtro searches the wiki, reads the expenses policy page, and answers with the claim limit and the approval step, linking the page it read.
Ask your Wiki.js what a page says, and who changed it last.
Connect Wiki.js 2.x with your host and an API key and Memtro searches and reads pages with tags, a page's edit history and its comments. Authors' email addresses and commenters' IP addresses are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can create, edit, move, convert, restore or delete pages, comment, rename tags, and create folders or rename files in the asset library. Deleting a page, comment, tag or uploaded file is permanent, and a published page is visible at once.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Wiki.js tool, reads what it needs, and answers with the source cited.
These tools change something in Wiki.js. 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 Wiki.js 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 does our onboarding page say about laptop setup?
Who changed the expenses policy page last, and when?
Which pages are tagged security?
What changed in the wiki this week?
Restore the previous version of the on-call runbook
A new starter at Brightwave Ltd asks how to claim travel expenses. Memtro searches the wiki, reads the expenses policy page, and answers with the claim limit and the approval step, linking the page it read.
Priya Nair notices the on-call runbook lost a section yesterday. Memtro reads the page history, shows that Dan Fletcher's edit removed it, and with the action granted restores the earlier version, which stays in the history.
The teams that lean on Wiki.js most, a question each of them asks, and what they connect beside it.
A record in Wiki.js 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.
Wiki.js 2.x only. As a Wiki.js administrator open Administration → API Access, make sure API access is enabled, and create a key named Memtro with an expiry
Choose a group for the key: read pages and source to read, write pages and comments to edit. Tag and asset changes need the matching manage permissions. Full access is not needed and not advised
In Connections → Wiki.js in Memtro type the wiki's name in Host only, public with a trusted certificate, and paste the API key, which is shown once
Ask what changed in the wiki this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Wiki.js tools are the same everywhere.
Only when you ask, and only what it has been granted: create a page (unpublished unless asked); edit a page (the new text replaces the old, which stays in the page's history); move a page to a new path; restore an earlier version of a page over the current one; delete a page; comment on a page; edit a comment; delete a comment; rename a tag or change its title across the wiki; delete a tag (removed from every page); convert a page to another editor format; create an asset folder; rename an uploaded file; delete an uploaded file. 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.
Host and API key. Wiki.js 2.x only. As a Wiki.js administrator open Administration → API Access, make sure API access is enabled, and create a key named Memtro with an expiry.
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