Who is reading
The founder asks how the newsletter is doing. Memtro reports the member totals by free, paid and comped, the newest sign-ups with their tier and open rate, and which posts went out as email this month.
Posts, members and newsletters from Ghost, remembered, and published when you ask.
Connect a Ghost site with a custom integration's Admin API key and Memtro reads posts and pages by status, tag or author, one post's full text, member totals by free, paid and comped, and your newsletters. Each new published post syncs in hourly as an event in memory. When you ask, and once an administrator has granted each action by name, it can draft, edit, schedule, publish or unpublish posts and pages, and add or edit members. Publishing makes a post public, emailing it to a newsletter's subscribers cannot be recalled, and deleting a post or page is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Ghost tool, reads what it needs, and answers with the source cited.
These tools change something in Ghost. 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 Ghost 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 we publish in October, and who wrote each post?
How many paid members do we have, and who joined in the last week?
Which drafts are sitting unpublished right now?
Draft a post titled 'Introducing team reports' from these notes
Publish the team reports post and email it to the Weekly newsletter
The founder asks how the newsletter is doing. Memtro reports the member totals by free, paid and comped, the newest sign-ups with their tier and open rate, and which posts went out as email this month.
Rachel Ford asks Memtro for a post about the new pricing, written from last week's announcement, and reads the draft in Ghost Admin. When she asks Memtro to publish it to the Weekly newsletter, the post goes public on the site and Ghost emails it to that newsletter's subscribers.
The teams that lean on Ghost most, a question each of them asks, and what they connect beside it.
A record in Ghost 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 Ghost Admin open Settings → Integrations → Add custom integration, name it (Memtro, say) and save
Copy the Admin API key, the long id:secret pair, not the Content API key. It has full Admin rights that Ghost does not scope, so Memtro publishes, emails, deletes or changes members only when you ask and an administrator has granted that action
In Memtro open Connections → Ghost, paste the Admin API key with the Site URL and connect. The key itself is never sent to Ghost, only a five-minute token signed with it
Ask how many paid members joined this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Ghost tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft post from markdown or HTML; edit a post's title, body, excerpt, tags or feature image; publish a post, optionally emailing it to a newsletter's members; schedule a post to publish (and optionally email) later; unpublish a post back to draft, or cancel its schedule; delete a post; create a draft page; edit, publish or unpublish a page; delete a page; add a member; edit a member's name, note, labels or newsletters. 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 Ghost records into memory as entities.
Site URL and Admin API key. In Ghost Admin open Settings → Integrations → Add custom integration, name it (Memtro, say) and save.
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