Ghost
Create, read, update and delete posts, pages, members and tags on a Ghost site via the Admin API.
About
Ghost ships in the w6w first-party pack. It declares 11 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.ghost- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Content Management · Productivity
Overview
Ghost is a self-hosted publishing platform, and this app manages content on a Ghost site through its Admin API: creating, updating, and deleting posts and pages, listing members and the subscription tiers they belong to, and reading and applying tags. It is built for workflows that publish or maintain content programmatically — scheduling a post, syncing tags from another system, or keeping a members list in view — rather than for a public-facing content widget, which is what Ghost’s separate read-only Content API is for.
Because every Ghost site lives at its own domain, this app connects to whichever install a user names rather than a fixed host, the same shape of problem as a self-hosted WordPress. Updating a post correctly requires knowing its current version to avoid overwriting someone else’s edit, which this app handles as part of the update rather than leaving it to the caller to get right.
Build with Ghost
Three routes to the same 11 actions. The Workflow tab is generated from Ghost's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Post
create-post Create a new post. HTML content is converted to Ghost's Lexical format on save.
Get Site Info
get-site-info Read the site's public title, description, logo and Ghost version. No auth needed.
List Members
list-members List members on a single page of results. Set `page` to walk further pages.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Ghost's real ids.
{
"manifestVersion": "2",
"name": "ghost-example",
"steps": [
{
"id": "create-member",
"uses": {
"app": "io.w6w.ghost",
"action": "create-member",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"email": "<email>"
}
}
]
}Here are some of the things you can do
-
Create Member
performcreate-member -
Create Post
performcreate-post -
Get Post
readget-post -
Get Site Info
readget-site-info -
List Members
readlist-members
+6 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Ghost, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Ghost. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "create-post",
payload: {
title: "<value>",
// html: "<value>",
// status: "<value>",
// publishedAt: "<value>",
// tags: "<value>",
// featureImage: "<value>",
// excerpt: "<value>",
// visibility: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-post --payload '{"title":"<value>"}'Give an AI agent Ghost — without giving it Ghost's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.ghost#create-member",
"input": {
"email": "<email>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Ghost connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Ghost's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Ghost itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Ghost declares its own checks, so its health is a property of the app rather than something the host guesses at.
Ghost platform status
Covers Ghost.org and Ghost(Pro)-hosted sites. Self-hosted installs are not represented here — see the `site` check for those.
API quota headroom
Site reachable
Unauthenticated `GET /ghost/api/admin/site/` against this connection's site — proves the host resolves AND that the Admin API is enabled.