Checking published copy
Priya Sharma, product marketing manager at Northwind, asked what the pricing page said about annual billing. Memtro opened the published page and quoted the paragraph from its pricing slice.
Which pages did we publish in Prismic last month, and what do they say?
Prismic connects Memtro to your repository's published pages. It reads content types, tags, languages and the releases the token can see, searches published pages by type, tag, words, language or date, and opens a page with its fields and slices, cut to 4,000 characters. With a write token, and when asked once an administrator has granted the action by name, it can create or update draft pages in a migration release, which a person reviews and publishes in Prismic, and edit a media asset's alt text, notes or credits. Deleting an asset is permanent and breaks pages that use it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Prismic tool, reads what it needs, and answers with the source cited.
These tools change something in Prismic. 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 Prismic, choosing the same kinds; the tab shows Prismic's own steps. Each event can start a job, with the event as its input. Prismic sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Prismic 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 blog posts were published last month?
What does the pricing page say?
Which pages are tagged case-study?
Which languages is the homepage published in?
Add alt text to the team photo on the about page.
Priya Sharma, product marketing manager at Northwind, asked what the pricing page said about annual billing. Memtro opened the published page and quoted the paragraph from its pricing slice.
Tom Reilly, content editor at Acme Ltd, asked Memtro to draft a case study page about Globex from his notes. Memtro created it as a draft in the migration release, tagged case-study. Nothing went live until Tom reviewed and published the release in Prismic.
The teams that lean on Prismic most, a question each of them asks, and what they connect beside it.
A record in Prismic 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.
Find the repository name in your Prismic address: acme for acme.prismic.io.
If the repository is private, go to Settings → API & Security → Access tokens in Prismic and copy a read token. For the write actions, also make a token under Settings → API & Security → Write APIs.
In Memtro, open Connections → Prismic and enter Repository name, Access token if you made one, and Write token only if Memtro may draft pages or edit assets.
Ask: which blog posts were published last month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Prismic tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft Prismic page in a migration release (not published); update a draft Prismic page's content, title and tags (not published); edit a Prismic media asset's alt text, notes or credits; delete a Prismic media asset (permanent, pages using it show a broken 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.
Repository name, with optional access and write tokens. Find the repository name in your Prismic address: acme for acme.prismic.io.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Prismic, choosing the same kinds; the tab shows Prismic'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