Ghost ghst CLI: The New AI-Native Admin Tool for Ghost CMS (Developer Beta)
Quick answer: ghst is Ghost's official new AI-native CLI tool (developer beta, 2026) that lets you manage your Ghost publication from the terminal — or hand control to an LLM like Claude or Codex. It handles posts, members, themes, newsletters, tiers, and social publishing, all without opening the admin panel.
If you run a Ghost site and spend time clicking through the admin panel to do the same things over and over — publishing updates, checking newsletter stats, managing member tiers — Ghost just released something worth paying attention to.
The Ghost team quietly announced a developer beta for ghst, a new CLI tool designed to interact with your Ghost publication from the command line. What makes it different from the existing Ghost CLI (which handles server install and updates) is the scope: ghst covers almost everything you'd normally do inside Ghost Admin — and it's built specifically to work with AI agents.
Forum reactions ranged from "this is timely!" to people immediately swapping out n8n automation workflows for it. Here's what it actually does, how it's different from older tools, and whether it's ready for your workflow yet.
What is the ghst CLI?
ghst is an official tool from the Ghost team, announced in March 2026 as a developer beta. Unlike the older ghost-cli package (which deals with server-level tasks like install, update, and restart), ghst is an admin-level tool — it interfaces with your Ghost publication's content and settings.
The announcement came directly from Ghost co-founder John O'Nolan, who described it as a way to let you — or an LLM — automate tasks inside Ghost using a set of pre-built tools. His phrasing was direct: "Pretty much everything you can do in Ghost Admin, you can do using this CLI."
The two tools serve different purposes:
| Tool | Purpose | Works with |
|---|---|---|
ghost-cli | Server-level install, update, restart, config | Self-hosted installs |
ghst | Admin-level content, members, themes, newsletters | Any Ghost instance (self-hosted or Ghost Pro) |
What can you actually do with ghst?
According to the official announcement, the tool covers most admin actions you'd normally click through manually:
- Posts: Create, edit, and publish posts directly from the terminal
- Members: Import or export member lists
- Themes: Download, upload, and activate themes without touching the admin UI
- Analytics: Query traffic data (e.g., "which post got the most traffic last month?")
- Newsletters: Check open rates on recent sends
- Social publishing: Post updates to the social web from Ghost
- Membership tiers: Create new paid tiers or special retention offers
The practical example O'Nolan gave: telling the tool out loud to "give [Jamie Larson] a complimentary subscription" — and having it handle the whole thing without opening a browser.
How does the LLM integration work?
This is where ghst stands apart from typical CLI tools. It's designed to be called by AI agents, not just humans typing commands. You can point Claude, Codex, or another LLM at the tool and give natural language instructions like:
ghst "find all posts published in the last 30 days with under 100 views and draft them"
Or give the tool to Claude Code and just talk to it. The demo O'Nolan shared shows the tool writing and publishing a post about cats — the point isn't that AI writes your content, but that you can script admin workflows in plain language.
Forum members immediately saw the connection. One user said they'd been building an n8n workflow to use as an MCP server and called ghst "a much better path." Another noted Claude Code had already changed how they think about CLI tools, and Ghost's easier to manage than WordPress even before this.
How does ghst compare to Ghost MCP?
There's already a community-built Ghost MCP server that lets Claude Desktop interact with Ghost through the Model Context Protocol. ghst is the official, first-party equivalent — with the difference that it runs as a CLI tool rather than an MCP server configuration.
| Option | Type | Official? | LLM support |
|---|---|---|---|
ghst | CLI (terminal) | Yes (Ghost team) | Claude, Codex, any agent |
| ghost-mcp | MCP server | Community | Claude Desktop |
| Ghost Admin API | REST API | Yes | Custom scripting |
If you're already using the Ghost Admin API via n8n, ghst can simplify that stack for tasks that don't need multi-step orchestration.
Is ghst safe to use?
The official announcement includes a clear warning: this tool supports destructive actions. Deleting posts, deleting members, wiping data — all possible. The team says there are confirmation steps and guardrails built in, but the disclaimer is explicit:
"This tool is currently only recommended for use by developers who are comfortable navigating terminal apps, and LLM / bash permissions."
A few practical precautions if you try it:
- Run a Ghost backup before testing anything that touches members or published content
- Start with read-only queries (analytics, newsletter stats) before letting it write or delete
- If you're using it with an LLM, review the action it's about to take before approving
- Don't run it with admin credentials in a shared environment unless you fully control what gets executed
O'Nolan noted he's been using it in production for a few weeks with no issues — but "in production for a few weeks" is not the same as battle-tested across thousands of installs.
How do I install ghst?
As of March 2026, ghst is in developer beta. The official thread on the Ghost forum is the primary source for installation details. It's built around the Ghost Admin API, which means it works with self-hosted Ghost installs and Ghost Pro alike — as long as you have admin credentials.
Follow the official thread at forum.ghost.org for install instructions and updates as the tool moves out of beta.
What workflows is it best for?
Based on the forum discussion and the announced feature set, ghst makes the most sense for:
- Bulk operations: Importing or exporting members, batch-editing post metadata
- Scripted publishing: Automating post creation from data sources or AI pipelines
- Quick admin tasks: Changing membership tiers, generating gift links, pulling stats — without a browser
- LLM-driven site management: Letting Claude or Codex handle recurring Ghost admin chores on your behalf
For teams already using n8n with Ghost, it's worth evaluating whether ghst handles your use case more cleanly — especially for anything that currently requires multiple API calls chained together.
Related Ghost Guides
- How to Connect Ghost CMS to n8n — if you're automating Ghost with workflows, compare this with what ghst can handle natively
- Ghost CMS Restart Not Working — the server-side CLI (ghost-cli) context for comparison
- How to Connect Ghost CMS to Bluesky — ghst can post to the social web, including Bluesky
- How to Restrict Content to Specific Membership Tiers — ghst can create and manage tiers via CLI
- Ghost CMS Retention Offers — create special offers without the admin UI
- Ghost Installation on Ubuntu — server setup context for self-hosters who'd use ghst
Frequently Asked Questions
What is the difference between ghost-cli and ghst?
ghost-cli manages the Ghost server — installation, updates, starting, stopping, and config on a self-hosted machine. ghst manages your Ghost publication's content and admin settings. They operate at completely different levels: server vs. admin. You might use both on a self-hosted install.
Does ghst work with Ghost Pro or only self-hosted?
ghst works through the Ghost Admin API, which is available on both Ghost Pro and self-hosted installs. You just need admin credentials. ghost-cli, by contrast, is self-hosted only since it needs direct server access.
Can I use ghst without an AI/LLM?
Yes. ghst is a standard CLI tool you can use directly in the terminal with regular commands. The LLM integration is an additional layer — it's not required. You can script it, run it in cron jobs, or use it interactively without any AI involved.
Is ghst safe to run on a production site?
The Ghost team says it works with multiple safety guardrails and confirmation steps, and O'Nolan has used it in production. That said, it supports destructive actions, so always back up your Ghost site before running any command that writes or deletes data. Treat it like any powerful admin tool.
How does ghst compare to the Ghost MCP server?
Ghost MCP is a community-built Model Context Protocol server that integrates with Claude Desktop specifically. ghst is the official first-party CLI that works with any LLM or no LLM at all. They overlap in use case but differ in architecture — MCP is server-based, ghst is a command line tool you call directly.
What AI tools work with ghst?
The official announcement mentions Claude and Codex as tested options, but any LLM or agent with bash/terminal access can call it. Claude Code, in particular, is well-suited since it understands CLI tools natively and can execute commands in context.
Where can I get ghst?
As of March 2026, ghst is in developer beta. The official release thread is at forum.ghost.org. Follow that thread for install instructions — the beta may have limited availability or require joining a waitlist.
Will ghst replace ghost-cli eventually?
They serve different purposes, so probably not a straight replacement. Ghost has announced that ghost-cli will be discontinued from v7 onwards, but ghst handles content administration, not server lifecycle management. There will likely be a separate server management solution (possibly Docker-based) to replace the server-side CLI.
If you manage Ghost at any scale — multiple members, regular publishing, recurring admin tasks — ghst is worth testing the moment it exits beta. The ability to script common admin actions, or hand them to an LLM, removes a surprising amount of browser-based friction. Start with low-risk, read-only commands, build confidence, then automate the repetitive stuff.