A content audit
Maya Okafor, content lead at Northwind, asked which blog posts still mentioned the old pricing. Memtro searched titles and bodies for pricing and listed the matching posts with their status and publish dates.
What did we publish on the blog this month, and which pages mention pricing?
ButterCMS shows you your blog posts with title, status, dates, author, categories, tags, summary and body. Memtro also reads pages of each page type with their fields, collection items, and the authors, categories and tags. When asked and granted, it can create, update or delete blog posts and collection items, and create or update pages, as drafts or published. ButterCMS can tell Memtro when a post or page is published or deleted, and a job can start. Writing needs the Write API add-on, on Advanced and Professional plans only.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ButterCMS tool, reads what it needs, and answers with the source cited.
These tools change something in ButterCMS. 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 ButterCMS, choosing the same kinds; the tab shows ButterCMS's own steps. Each event can start a job, with the event as its input. ButterCMS sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce ButterCMS 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 was published on the blog this month?
Which blog posts mention pricing?
What does the About page say about our history?
Which items are in the team members collection?
Draft a blog post announcing the new Leeds office.
Maya Okafor, content lead at Northwind, asked which blog posts still mentioned the old pricing. Memtro searched titles and bodies for pricing and listed the matching posts with their status and publish dates.
At Acme Ltd, a job starts when ButterCMS reports that a blog post was published. It reads the post's title, summary, categories and SEO fields. Sarah Chen, marketing manager, gets a short note that the post is live, with anything missing from its SEO fields.
The teams that lean on ButterCMS most, a question each of them asks, and what they connect beside it.
A record in ButterCMS 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 ButterCMS, open Settings → General → API Tokens and copy the read API token. Free and trial accounts have a monthly API call cap.
Open Connections → ButterCMS in Memtro and paste the Read API token. Add the Write API token only if Memtro should create or change content.
An administrator grants actions such as publish a blog post by name to the teams that may use them. Once ButterCMS support has enabled webhooks, events are turned on from the connection's Events tab, and the address is added in ButterCMS's webhook settings.
Ask what was published on the blog this month.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ButterCMS tools are the same everywhere.
Only when you ask, and only what it has been granted: create a blog post, as a draft or published; change a blog post's content, categories, tags or status; delete a blog post (soft delete, its slug is freed); create a page of an existing page type, as a draft or published; change a page's fields or status; add an item to a collection, as a draft or published; change a collection item's fields or status; delete a collection item (soft delete). 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.
Read API token. In ButterCMS, open Settings → General → API Tokens and copy the read API token. Free and trial accounts have a monthly API call cap.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ButterCMS, choosing the same kinds; the tab shows ButterCMS'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