What went live
A marketer asks what changed on the site since Monday. Memtro lists the entries published or updated, newest first, with their content type and a link to each in the Contentful web app.
Your Contentful content, searchable, remembered as it changes and edited when you ask.
Connect Contentful with a Content Delivery API token and the space ID, and Memtro reads what the website shows: the content model, published entries by type with search and field filters, one entry in full with linked entries and assets resolved, and the asset library. The hourly sync records each entry published or updated in memory. Add a Content Management API token, and once an administrator has granted each action by name, it can draft and edit entries, publish them to the live website or unpublish them, and archive them when you ask. Deleting an entry is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Contentful tool, reads what it needs, and answers with the source cited.
These tools change something in Contentful. 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, choose the kinds you want, and Memtro registers its address with Contentful for you. Each event can start a job, with the event as its input. Contentful signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Contentful 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 did the content team publish or update in the last 7 days?
Find the blog post with the slug 'pricing-update-2026' and give me its full text
Which case studies mention Acme Logistics?
What fields does the landingPage content type have?
Fix the typo in the returns policy headline and publish it
A marketer asks what changed on the site since Monday. Memtro lists the entries published or updated, newest first, with their content type and a link to each in the Contentful web app.
Hugo Marsh in support spots that the returns policy page says 14 days instead of 30 and asks Memtro to correct it. Memtro reads the entry, changes the field as a draft, and publishes that version when Hugo confirms, so the website serves the new wording and the space's webhooks fire.
The teams that lean on Contentful most, a question each of them asks, and what they connect beside it.
A record in Contentful 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.
In Contentful open Settings → API keys → Add API key and copy the Content Delivery API access token (not the Preview or Management one) and the Space ID shown beside it
For the actions, create a personal access token under Account settings → CMA tokens. It acts as you with your space role's rights, so leave it out to keep Memtro read-only
In Memtro open Connections → Contentful, paste the Content Delivery API access token and the Space ID, add the Content Management API token if wanted, leave Environment blank for master, and connect
Ask what the content team published this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Contentful tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft entry, or change an entry's fields; publish an entry to the website, or unpublish it; archive or unarchive an entry; delete an entry permanently. 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. An hourly sync anchors recently changed Contentful records into memory as entities.
Content Delivery API access token and Space ID. In Contentful open Settings → API keys → Add API key and copy the Content Delivery API access token (not the Preview or Management one) and the Space ID shown beside it.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Contentful for you. 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