Who changed this
The content lead asks why the Brightwave Ltd pricing changed overnight. Memtro reads the activity log for that item and shows an update at 22:14 by Dan Fletcher, with the collection and the time of each earlier change.
Ask Directus for items in any collection, and who changed what and when.
Connect Directus with your host name and a static token and Memtro reads your own data model: collections, items, files, users, versions, activity and comments. Memtro talks to your server or your Directus Cloud address, and the token has exactly its user's permissions. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create, change and permanently delete items and files, manage comments, promote a content version to live, invite people by email, and suspend or permanently delete users. Writes run your Directus Flows and hooks.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Directus tool, reads what it needs, and answers with the source cited.
These tools change something in Directus. 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 Directus 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.
Which articles in the posts collection are still in draft?
Who changed the Northwind product record, and when?
What fields does the events collection have?
Set the status of the Acme case study item to archived
Invite Priya Nair to Directus as an editor
The content lead asks why the Brightwave Ltd pricing changed overnight. Memtro reads the activity log for that item and shows an update at 22:14 by Dan Fletcher, with the collection and the time of each earlier change.
Priya Sharma asks Memtro to publish the approved version of the Northwind case study. Memtro compares the version with the live item, then promotes it, so its changes replace the live item and Directus runs the Flows set on that collection.
The teams that lean on Directus most, a question each of them asks, and what they connect beside it.
A record in Directus 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.
Create a dedicated Directus user for Memtro with a role that can see, and if wanted change, only the collections, files and users it should
In Directus open User Directory → that user → Token, generate a token, copy it and save the user. The token does not expire
In Connections → Directus in Memtro type your Host name only, with no https://, path or port (on Cloud, your project's address), and paste the Static token
Ask who changed the pricing collection this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Directus tools are the same everywhere.
Only when you ask, and only what it has been granted: create an item in a Directus collection; change fields of a Directus item; delete a Directus item; add a comment to a Directus item; edit a Directus comment; delete a Directus comment; change a Directus file's title, description, download name, folder or tags; delete a Directus file; create a folder in the Directus file library; invite a person to Directus by email with a role; suspend or reactivate a Directus user; delete a Directus user; promote a Directus content version to the live item. 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 Static token. Create a dedicated Directus user for Memtro with a role that can see, and if wanted change, only the collections, files and users it should.
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