[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Ghost API and MCP server

> Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). The Admin API covers posts, pages, members, labels, newsletters, tiers and offers, and Ghost says everything Ghost Admin can do is also possible with the API. You make an integration key or staff access token, sign a short-lived token from it on every call, and build the agent tool layer yourself.

Open source publishing platform for newsletters and memberships: posts, free and paid members, email newsletters and tiers in one site, hosted by Ghost(Pro) or on your own server.

## What is the Ghost API?

Cotlet's Ghost API exposes 14 endpoints for your own Ghost account: list posts, get a post, list members, get a member, list newsletters, list tiers, list labels, list tags, create a draft post, update a post, schedule a post, publish a post now, add or remove a label and unsubscribe members from email. The list_posts endpoint returns list posts with their status, tags and publish date. Each endpoint takes simple JSON inputs like post_id, page or limit and works both as an operation of the ghost_read or ghost_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 14 (8 read, 6 write)
- **Updated:** 2026-10-20

Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Ghost with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Ghost have an official API?

Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). The Admin API covers posts, pages, members, labels, newsletters, tiers and offers, and Ghost says everything Ghost Admin can do is also possible with the API. You make an integration key or staff access token, sign a short-lived token from it on every call, and build the agent tool layer yourself.

| Task | Ghost official | Cotlet |
|---|---|---|
| List and read posts | Yes: Admin API, 15 records per page by default | Yes |
| Create a draft post from text or HTML | Yes: Admin API; HTML is converted to Lexical and the conversion is lossy | Yes |
| Schedule or publish a post and send it as a newsletter | Yes: Admin API, with the newsletter slug and an optional member segment | Yes |
| List members by status, label or open rate | Yes: Admin API filters; you write the filter syntax yourself | Yes |
| Find where a member signed up | Partly: Attribution comes back only from the single-member read endpoint | Yes |
| Add or remove member labels | Yes: Admin API, one member at a time | Yes |
| Unsubscribe members from newsletters | Yes: Admin API, by updating the newsletters of each member | Yes |
| List newsletters, tiers and tags | Partly: Newsletters and tiers have endpoints; tags are handled inside posts | Yes |

Sources: [Ghost Developer Docs: Admin API overview](https://docs.ghost.org/admin-api), [Ghost Developer Docs: Sending a post via email](https://docs.ghost.org/admin-api/posts/sending-a-post), [Ghost Developer Docs: Members](https://docs.ghost.org/admin-api/members/overview), [Ghost Help: Member management](https://ghost.org/help/member-management/)

## For AI agents

```text
Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). The Admin API covers posts, pages, members, labels, newsletters, tiers and offers, and Ghost says everything Ghost Admin can do is also possible with the API. You make an integration key or staff access token, sign a short-lived token from it on every call, and build the agent tool layer yourself.
Cotlet provides a hosted MCP server and REST API for Ghost: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=ghost, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    ghost_read, ghost_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/ghost, each operation at its own route, e.g. POST /api/v1/ghost/draft-posts
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_posts, get_post, list_members, get_member, list_newsletters, list_tiers, list_labels, list_tags, create_draft_post, update_post, schedule_post, publish_post, label_members, unsubscribe_members
Confirm      update_post, schedule_post, publish_post, unsubscribe_members (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/ghost-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=ghost, requests Ghost in the Cotlet console and creates an API key there.
2. The user signs in to Ghost once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Ghost for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Ghost server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Ghost MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Ghost in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Ghost only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Ghost login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Ghost's terms; Cotlet is not affiliated with Ghost.
```

## What can an AI agent do in Ghost?

Cotlet is best for newsletter publishers and small editorial teams who want an AI agent to draft, schedule and send Ghost posts and tidy their member list without running or fixing a server, or minting Admin API tokens.

- **[Schedule newsletter posts](https://cotlet.dev/integrations/ghost-api-mcp-server/schedule-newsletter-posts.md)** (runs: weekly): "Write this week's issue from my notes below as a Ghost draft tagged "Weekly". Check the draft with me, then schedule it for Monday 9:00 and send it to all members on the weekly newsletter." → `list_newsletters`, `list_tags`, `create_draft_post`, `get_post`, `schedule_post`
- **[Label members by signup source](https://cotlet.dev/integrations/ghost-api-mcp-server/label-members-by-signup-source.md)** (runs: weekly): "List the Ghost members who signed up on the post "launch-week" in the last 7 days and add the label "Launch signup" to them. Tell me how many you labelled and how many already had it." → `list_labels`, `list_members`, `label_members`
- **[Unsubscribe unengaged members](https://cotlet.dev/integrations/ghost-api-mcp-server/unsubscribe-unengaged-members.md)** (runs: weekly): "Find free Ghost members who got at least 10 emails and opened none of them. Show me the list first. After I say yes, unsubscribe them from email." → `list_members`, `get_member`, `unsubscribe_members`
- **Review tiers and who is on them** (runs: weekly): "List my Ghost tiers with their monthly and yearly prices, then count members by status: free, paid, comped and gift. Compare with last week if you have the numbers." → `list_tiers`, `list_members`
- **Tidy tags on draft posts**: "Go through my Ghost drafts. If a tag looks like a near-duplicate of an existing one, such as "newsletter" next to "Newsletter", replace it with the existing tag and tell me what you changed." → `list_posts`, `list_tags`, `update_post`

## Can Ghost automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Ghost connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to schedule newsletter posts, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/ghost/newsletters. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/ghost/newsletters with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Ghost.

### list_posts

List posts with their status, tags and publish date. Access: read. REST: `GET /api/v1/ghost/posts`. MCP: `ghost_read → list_posts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | draft, published or scheduled. Omit for all. |
| `tag` | string | no | Tag slug to filter by. |
| `order` | string | no | Sort order such as published_at desc. Default is newest first. |
| `page` | integer | no | Page number, starting at 1. The response meta says how many pages there are. |
| `limit` | integer | no | Records per page, 100 at most. Default 15. |

Returns id, title, slug, status, access, tags, authors, published_at and updated_at for each post, plus the pagination meta. The body is left out; get_post returns it. Which posts you see follows your staff role.

Example response:

```json
{
  "posts": [
    {
      "id": "6710a1c2f3e4d500a1b2c3d4",
      "title": "Issue 42: pricing notes",
      "slug": "issue-42-pricing-notes",
      "status": "draft",
      "tags": [
        "Weekly"
      ],
      "published_at": null,
      "updated_at": "2026-10-17T08:12:44.000Z"
    }
  ],
  "meta": {
    "page": 1,
    "limit": 15,
    "pages": 1,
    "total": 1
  }
}
```

### get_post

Read one post with its content, tags, authors and email status. Access: read. REST: `GET /api/v1/ghost/posts/{post_id}`. MCP: `ghost_read → get_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `post_id` | string | yes | Post ID from list_posts. |
| `format` | string | no | html or lexical. Default html. |

Returns the full post: title, content, excerpt, access, tags, authors, status and published_at. A post that was sent as a newsletter also carries the email status, with the delivered and opened counts Ghost holds for it. Needs a role that can see the post.

Example response:

```json
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "status": "draft",
    "access": "Public",
    "tags": [
      "Weekly"
    ],
    "authors": [
      "Sam Rivera"
    ],
    "excerpt": "Three pricing changes we tried this month.",
    "published_at": null,
    "updated_at": "2026-10-17T08:12:44.000Z"
  }
}
```

### list_members

List members, filtered by status, label, signup post, email activity or last visit. Access: read. REST: `GET /api/v1/ghost/members`. MCP: `ghost_read → list_members`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | free, paid, comped or gift. Omit for all. |
| `label` | string | no | Label name to filter by. |
| `signed_up_on` | string | no | Slug of the post or page the member signed up on. |
| `created_after` | string | no | ISO 8601 date. Only members created after it. |
| `min_emails_sent` | integer | no | Only members who received at least this many emails. |
| `max_open_rate` | integer | no | Only members whose open rate is at most this percentage, 0 to 100. Members without a rate are left out. |
| `page` | integer | no | Page number, starting at 1. The response meta says how many pages there are. |
| `limit` | integer | no | Records per page, 100 at most. Default 15. |

Returns id, email, name, status, labels, created_at, last_seen_at, email_count, email_opened_count and email_open_rate for each member, newest first, plus the pagination meta. The email_open_rate is null while Ghost has sent too few emails to work one out. Member emails are personal data; they stay in the response and are not stored by Cotlet.

Example response:

```json
{
  "members": [
    {
      "id": "6710b2d4a1b2c300a1b2c3e1",
      "email": "reader1@example.com",
      "name": "Reader One",
      "status": "free",
      "labels": [],
      "created_at": "2026-10-14T10:02:11.000Z",
      "last_seen_at": "2026-10-16T18:40:00.000Z",
      "email_count": 2,
      "email_opened_count": 1,
      "email_open_rate": 50
    }
  ],
  "meta": {
    "page": 1,
    "limit": 15,
    "pages": 3,
    "total": 38
  }
}
```

### get_member

Read one member with subscriptions, newsletters and signup source. Access: read. REST: `GET /api/v1/ghost/members/{member_id}`. MCP: `ghost_read → get_member`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `member_id` | string | yes | Member ID from list_members. |

Returns the member profile: status, labels, newsletters they are subscribed to, tiers, subscriptions, email stats and the signup attribution Ghost keeps. For a paid member the subscription shows the tier, interval and renewal date. Billing details stay in Stripe.

Example response:

```json
{
  "member": {
    "id": "6710c3e5b1c2d400a1b2c4f1",
    "email": "reader2@example.com",
    "status": "free",
    "labels": [],
    "newsletters": [
      "weekly-roundup"
    ],
    "email_count": 14,
    "email_opened_count": 0,
    "last_seen_at": "2026-10-15T07:30:00.000Z",
    "attribution": {
      "type": "post",
      "title": "Launch week",
      "url": "https://example.com/launch-week/"
    }
  }
}
```

### list_newsletters

List the newsletters of the site with their slugs. Access: read. REST: `GET /api/v1/ghost/newsletters`. MCP: `ghost_read → list_newsletters`.

No parameters.

Returns name, slug, description, status (active or archived) and the sender name for each newsletter. A site has one newsletter by default. The slug is what schedule_post and publish_post take.

Example response:

```json
{
  "newsletters": [
    {
      "id": "62750bff2b868a34f814af08",
      "name": "Weekly roundup",
      "slug": "weekly-roundup",
      "status": "active",
      "sender_name": "Sam Rivera"
    }
  ]
}
```

### list_tiers

List the free and paid tiers with prices and benefits. Access: read. REST: `GET /api/v1/ghost/tiers`. MCP: `ghost_read → list_tiers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `include_archived` | boolean | no | Also return archived tiers. Default false. |

Returns name, type (free or paid), monthly and yearly price, currency, benefits and visibility for each tier. Prices are in the smallest currency unit, as Ghost stores them. Members on an archived tier stay subscribed and keep renewing.

Example response:

```json
{
  "tiers": [
    {
      "id": "622727ad96a190e914ab6665",
      "name": "Bronze",
      "type": "paid",
      "monthly_price": 500,
      "yearly_price": 5000,
      "currency": "usd",
      "benefits": [
        "Free daily newsletter",
        "3 posts a week"
      ],
      "active": true
    }
  ]
}
```

### list_labels

List member labels, with how many members carry each. Access: read. REST: `GET /api/v1/ghost/labels`. MCP: `ghost_read → list_labels`.

No parameters.

Returns the name and slug of each label and the member count. Use it before label_members so the agent reuses an existing label name and does not create a near-duplicate.

Example response:

```json
{
  "labels": [
    {
      "id": "6958473e4c66da000199e33e",
      "name": "VIP",
      "slug": "vip",
      "members": 12
    }
  ]
}
```

### list_tags

List the tags used on posts, with how many posts carry each. Access: read. REST: `GET /api/v1/ghost/tags`. MCP: `ghost_read → list_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `page` | integer | no | Page number, starting at 1. The response meta says how many pages there are. |
| `limit` | integer | no | Records per page, 100 at most. Default 15. |

Returns the name, slug and post count of each tag, including internal tags that start with a hash. Ghost creates a tag it cannot match by name when a post is saved, so this list is the check against typos and near-duplicates.

Example response:

```json
{
  "tags": [
    {
      "name": "Weekly",
      "slug": "weekly",
      "posts": 41
    },
    {
      "name": "Product",
      "slug": "product",
      "posts": 17
    }
  ]
}
```

### create_draft_post

Create a post as a draft. Nobody sees it until it is published or scheduled. Access: write. REST: `POST /api/v1/ghost/draft-posts`. MCP: `ghost_write → create_draft_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Post title. |
| `content` | string | yes | Post body. HTML or Markdown. |
| `tags` | string[] | no | Tag names. A name Ghost cannot match becomes a new tag. |
| `access` | string | no | Who can read it: Public, Members only, Paid-members only or Specific tiers. Default Public. |
| `excerpt` | string | no | Custom excerpt shown under the title. |

Returns the saved draft with its id, slug, tags and authors. The author defaults to the staff user you signed in as. HTML is converted to the editor format and some markup can come out different, so read the draft back with get_post. A draft reaches nobody and you remove it from Ghost Admin, so this tool does not ask for confirmation.

Example response:

```json
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "slug": "issue-42-pricing-notes",
    "status": "draft",
    "access": "Public",
    "tags": [
      "Weekly"
    ],
    "authors": [
      "Sam Rivera"
    ],
    "published_at": null
  }
}
```

### update_post

Change the title, content, tags, access or excerpt of an existing post. Access: write, asks the user first. REST: `PATCH /api/v1/ghost/posts/{post_id}`. MCP: `ghost_write → update_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `post_id` | string | yes | Post ID from list_posts. |
| `title` | string | no | New title. |
| `content` | string | no | New body. Replaces the old one. |
| `tags` | string[] | no | Full list of tag names. It replaces the current tags, it does not add to them. |
| `access` | string | no | Public, Members only, Paid-members only or Specific tiers. |
| `excerpt` | string | no | New custom excerpt. |

Returns the updated post. The tool reads the post first and refuses to overwrite it if someone saved it in the meantime. On a published post the change is visible to readers at once, which is why it asks. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "status": "draft",
    "tags": [
      "Weekly",
      "Product"
    ],
    "updated_at": "2026-10-17T09:05:10.000Z"
  }
}
```

### schedule_post

Schedule a draft to publish at a future time, with an optional newsletter send. Access: write, asks the user first. REST: `POST /api/v1/ghost/posts/{post_id}/schedule`. MCP: `ghost_write → schedule_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `post_id` | string | yes | Post ID from list_posts. |
| `publish_at` | string | yes | ISO 8601 date and time in the future, for example 2026-10-19T09:00:00.000Z. |
| `newsletter` | string | no | Newsletter slug from list_newsletters. Omit to publish on the site without an email. |
| `send_to` | string | no | With a newsletter: all, free or paid members. Default all. |

Returns the post with status scheduled and the time it will go out. At that time Ghost publishes the post and sends the email. A time in the past is rejected. Only a role that can publish may call it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "status": "scheduled",
    "published_at": "2026-10-19T09:00:00.000Z",
    "newsletter": "weekly-roundup",
    "send_to": "all"
  }
}
```

### publish_post

Publish a draft now, with an optional newsletter send. Access: write, asks the user first. REST: `POST /api/v1/ghost/posts/{post_id}/publish`. MCP: `ghost_write → publish_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `post_id` | string | yes | Post ID from list_posts. |
| `newsletter` | string | no | Newsletter slug from list_newsletters. Omit to publish on the site without an email. |
| `send_to` | string | no | With a newsletter: all, free or paid members. Default all. |

Returns the post with status published and, when a newsletter was given, the email status. The post goes public and the email is queued at once, and neither can be recalled. If the email comes back as failed, the post goes back to draft first and is published again. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "status": "published",
    "published_at": "2026-10-17T09:30:00.000Z",
    "email": {
      "status": "submitted",
      "recipient_filter": "all"
    }
  }
}
```

### label_members

Add a label to members, or remove it from them. Access: write. REST: `POST /api/v1/ghost/members/label`. MCP: `ghost_write → label_members`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `action` | string | yes | add or remove. |
| `label` | string | yes | Label name. With add, a label that does not exist yet is created. |
| `member_ids` | string[] | yes | Member IDs from list_members. |

Returns how many members were changed and how many already had the state you asked for. Labels are internal and no member sees them, and a second call with the other action undoes the first, so this tool does not ask for confirmation. Members are updated one by one, and the response lists any that failed.

Example response:

```json
{
  "label": "Launch signup",
  "action": "add",
  "updated": 3,
  "skipped": 0,
  "failed": []
}
```

### unsubscribe_members

Turn off newsletter emails for the given members. Access: write, asks the user first. REST: `POST /api/v1/ghost/members/unsubscribe`. MCP: `ghost_write → unsubscribe_members`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `member_ids` | string[] | yes | Member IDs from list_members. |

Returns how many members were unsubscribed. Their account and tier stay as they are, and they can subscribe again in their account or you can switch the Subscribed to newsletter toggle in their profile. It changes what real people receive, so the agent should show the list first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "unsubscribed": 3,
  "skipped": 0,
  "failed": []
}
```

## How do I connect Ghost to Claude Code, Codex or Cursor?

Connecting Ghost takes three steps: sign up, sign in to Ghost once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Ghost to your agent.

1. **Create an account** Sign up and add Ghost in the console. Your API key is there too.

2. **Sign in to Ghost in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Ghost there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Ghost tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Write this week's issue from my notes below as a Ghost draft tagged "Weekly". Check the draft with me, then schedule it for Monday 9:00 and send it to all members on the weekly newsletter.
```

### Call Ghost from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/ghost with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/ghost/draft-posts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Issue 42: pricing notes","content":"<p>Three pricing changes we tried this month.</p>","tags":["Weekly"],"access":"Public"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "post": {
    "id": "6710a1c2f3e4d500a1b2c3d4",
    "title": "Issue 42: pricing notes",
    "slug": "issue-42-pricing-notes",
    "status": "draft",
    "access": "Public",
    "tags": [
      "Weekly"
    ],
    "authors": [
      "Sam Rivera"
    ],
    "published_at": null
  }
}
```

## Why use Cotlet for Ghost?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Ghost yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Ghost changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Ghost to Cotlet?

Yes. You sign in to Ghost yourself, in your own Cloud Browser, and we never save your password. Your agents only get Ghost once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Ghost integration?**

No, Cotlet is independent of Ghost. Ghost's own API is too limited for this work. Cotlet works through your own Ghost account, the way you use Ghost in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Ghost in your console: your agents lose access at once and you stay signed in. Signing out of Ghost in the browser works too, and Reset browser deletes the whole profile.

## Is there a Ghost MCP server on GitHub?

Yes. Community Ghost MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it an Admin API key, and fix it when Ghost changes. Cotlet hosts the same kind of server for you, signs in as your staff user, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create a custom integration in Ghost Admin, store its Admin API key, add the server to each MCP client | Sign up, sign in to Ghost Admin once, add one MCP server or API key |
| When Ghost changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Ghost access | Admin API key in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you regenerate the key or sign in again by hand | Your Cloud Browser keeps you signed in; if Ghost logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Ghost changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Ghost API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Ghost API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Ghost account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Ghost yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Ghost only after you enable it. When Ghost signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Ghost, sign out of Ghost in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Ghost's terms:** You use your own Ghost account and stay responsible for following Ghost's terms. Cotlet is independent and not affiliated with Ghost. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Ghost in the console and press Request access. Then you create your API key and connect Ghost there.

**Do I need to be technical?**

No. You sign in to Ghost once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Ghost to Cotlet?**

Yes. You sign in to Ghost yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Ghost once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Ghost sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Ghost cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Ghost's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Ghost sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Ghost login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Ghost offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Ghost role does my agent need?**

It follows the staff login you connect. Contributors can write posts but cannot publish, Authors can create and publish posts and tags, Editors can manage authors and contributors, and Administrators have full permissions to edit all data and settings.

**Do newsletters send if I run Ghost on my own server?**

Only with a bulk email provider. Self-hosted Ghost sends newsletters through Mailgun, set up under Email newsletter settings, and basic SMTP is not enough. Ghost(Pro) includes email delivery.

**Which timezone does a scheduled post use?**

The one set in Settings > General in Ghost Admin. The schedule_post time is an ISO 8601 date and time, so include the offset or Z to be exact.

**Can my agent post or send messages in Ghost without asking me?**

No. Every call to update_post, schedule_post, publish_post or unsubscribe_members waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_draft_post, label_members runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Ghost API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/ghost from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.