Which blog posts changed this week and are not yet published?
Contentstack holds your site's content. Memtro reads content types, entries with locale, version, workflow stage and where each is published, an entry's own fields, assets, environments, releases, workflows, and the audit log of what changed. When asked and granted, it can create, update and delete entries, publish or unpublish entries and assets now or on a schedule, update and delete assets, set an entry's workflow stage, and create, fill and deploy releases. The audit log covers the last 30 days, and names and emails are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Contentstack tool, reads what it needs, and answers with the source cited.
These tools change something in Contentstack. 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 Contentstack 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 changed this week and are not yet published?
Where is the pricing page entry published, and in which locales?
What is in the spring launch release?
Who deleted entries in the last week, according to the audit log?
Publish the spring launch post to production.
Priya Sharma, a content lead at Acme Ltd, asked which blog posts had changed this week but were not yet published. Memtro listed the entries with their version, workflow stage and where each was last published, so she could see what was waiting.
Dan Fletcher, a web producer at Northwind, asked Memtro to deploy the spring launch release to production at nine on Monday. Memtro scheduled the deployment, and every entry in it went live on the production site together at that time.
The teams that lean on Contentstack most, a question each of them asks, and what they connect beside it.
A record in Contentstack 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.
Jotform
DataForSEO
Moz API
Hygraph
Paperform
Kajabi
Kontent.ai
Teachable
WufooIn your Contentstack stack, copy the API key from Settings → Stack → API Credentials. A stack Owner or Admin then creates a token under Settings → Tokens → Management Tokens, which is shown once.
In Memtro, open Connections → Contentstack and paste the Stack API key and the Management Token.
Set the Region if your organization does not sign in to North America, and a Branch if not the main one. An administrator grants the publish, delete and release actions by name to the teams that may use them.
Ask which blog posts changed this week and are not yet published.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Contentstack tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft entry; update an entry (saves a new version); delete an entry (permanent); publish an entry to environments; unpublish an entry from environments; publish an asset to environments; unpublish an asset from environments; update an asset's title or description; delete an asset (permanent); move an entry to a workflow stage; create a release; add an entry to a release; deploy a release to environments. 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.
Stack API key and Management Token. In your Contentstack stack, copy the API key from Settings → Stack → API Credentials. A stack Owner or Admin then creates a token under Settings → Tokens → Management Tokens, which is shown once.
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
