cogny clicmsfirst 15 calls free
ghost from your shell.
List and write Ghost posts and pages, manage tags and members, and read newsletter config — from Bash over the Ghost Admin API MCP. Publish to your publication from a script, no editor tab required.
- 1. sign up, free for the first calls (uses your git email)
npx @cogny/cli init --agent claude-code - 2. see every Ghost tool
cogny tools list - 3. call any tool from bash, no MCP wiring
cogny tools call mcp__Ghost__list_posts --input '{…}'
Drafting and scheduling in the Ghost editor is one post at a time in the browser. The CLI lets an agent draft, tag, and publish posts programmatically and pull your member list as JSON. Connect Ghost once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.
Start SoloSign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Ghost tool over JSON-RPC. The first 15 calls are free.
npx @cogny/cli init --agent claude-code
real Ghost tools.
Tool names as the Ghost MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.
- mcp__Ghost__list_posts
List posts with status and metadata.
cogny tools call mcp__Ghost__list_posts \ --input '{"limit":2,"status":"published"}'
example response
{ "posts": [ { "id": "65f1a", "title": "Why agents pick CLI-native tools", "slug": "agents-cli-native", "status": "published", "published_at": "2026-06-10T08:00:00.000Z" }, { "id": "65f0b", "title": "Reporting without dashboards", "slug": "reporting-without-dashboards", "status": "published", "published_at": "2026-06-03T08:00:00.000Z" } ], "meta": { "pagination": { "page": 1, "limit": 2, "total": 88 } } } - mcp__Ghost__create_post
Create a draft post with HTML and tags.
cogny tools call mcp__Ghost__create_post \ --input '{"title":"CLI-first content ops","html":"<p>Draft body…</p>","status":"draft","tags":["product"]}'
example response
{ "id": "66ab9", "title": "CLI-first content ops", "slug": "cli-first-content-ops", "status": "draft", "url": "https://blog.acme.com/p/66ab9/" } - mcp__Ghost__list_members
List subscribers/members of the publication.
cogny tools call mcp__Ghost__list_members \ --input '{"limit":2}'
example response
{ "members": [ { "id": "m_01", "email": "reader1@example.com", "name": "Reader One", "subscribed": true, "status": "free" }, { "id": "m_02", "email": "reader2@example.com", "name": "Reader Two", "subscribed": true, "status": "paid" } ], "meta": { "pagination": { "page": 1, "limit": 2, "total": 1340 } } }
the rest of the surface.
A sample of the other Ghost tools. Run cogny tools list --json for every tool and its input schema.
- mcp__Ghost__get_post
- mcp__Ghost__update_post
- mcp__Ghost__delete_post
- mcp__Ghost__list_pages
- mcp__Ghost__create_page
- mcp__Ghost__list_tags
- mcp__Ghost__create_tag
- mcp__Ghost__get_member
- mcp__Ghost__list_newsletters
calls from a script. verdicts from cogny.
Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.
- worked
Moved the number. Every measured win has a share card.
- partial
Some of it did.
- didn't work
On the record anyway, so it isn't proposed again.
- inconclusive
Not enough data to call.
questions.
- Is this an official Ghost CLI?
- No — the official `ghost` CLI manages self-hosted installs. This is the Cogny CLI calling the Ghost Admin API MCP over the cogny-mcp-proxy: content (posts, pages, tags) and membership tools driven from Bash. Ghost Foundation is not affiliated.
- Can it publish, not just draft?
- Yes. `create_post` / `update_post` accept a status (draft/published) and tags/authors, so an agent can draft, review, and publish to your Ghost site without opening the editor.
- Does it read members for newsletters?
- Yes — `list_members`, `get_member`, and `list_newsletters` expose your subscriber list and newsletter config as JSON, which you can pipe into an ESP or a segmentation step.
Building an agent? The full tool map for every server is one fetch: /cli/llms.txt