Before the launch
The marketing lead asks which launch articles are still drafts. Memtro reads the draft versions of the articles type, filtered by the launch tag, and lists four with their titles, locales and when each was last updated.
Ask Strapi which documents are drafts, published or missing a field.
Connect Strapi 5 with your host name and an API token and Memtro reads documents with filters, sorting and drafts, single types and the media library. 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 and change documents and single types, saved as a draft by default but live at once on a type without Draft & Publish, and change a media file's name, alternative text or caption. It can permanently delete documents, single type content and media files.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Strapi tool, reads what it needs, and answers with the source cited.
These tools change something in Strapi. 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 Strapi, choosing the same kinds; the tab shows Strapi's own steps. Each event can start a job, with the event as its input. Strapi sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Strapi 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 are still drafts?
What does the homepage single type say right now?
Which blog posts mention the Northwind partnership?
Create a draft article titled Acme joins the partner programme
Set the alternative text on the BigCo logo image to BigCo logo
The marketing lead asks which launch articles are still drafts. Memtro reads the draft versions of the articles type, filtered by the launch tag, and lists four with their titles, locales and when each was last updated.
Priya Nair asks Memtro to start an article about the BigCo case study. Memtro creates it as a draft, so the published site is unchanged until somebody publishes it in Strapi, and Strapi's webhooks fire as for any change.
The teams that lean on Strapi most, a question each of them asks, and what they connect beside it.
A record in Strapi 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.
Needs Strapi 5. Strapi 4 is not supported
In Strapi admin open Settings → Global settings → API Tokens → Create new API Token, name it Memtro and choose a duration. Read-only allows reading only. Creating, changing or deleting needs Full access or a Custom token with those actions ticked for the content types Memtro may use
In Connections → Strapi in Memtro type your Host name only, with no https://, /api or port (Cloud is <project>.strapiapp.com), paste the API token and list the plural API ids
Ask which articles are still drafts
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Strapi tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Strapi document (draft by default); change a Strapi document (draft by default); change a Strapi single type (draft by default); delete a Strapi document; delete a Strapi single type's content; delete a Strapi media file; change a Strapi media file's name, alternative text or caption. 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 token. Needs Strapi 5. Strapi 4 is not supported.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Strapi, choosing the same kinds; the tab shows Strapi'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