NEW: the postqueen MCP server is live. Connect it in a minute
postqueen
Listmonk

Automate Listmonk with Cursor

Schedule Listmonk campaigns without leaving your editor. Cursor's agent drives postqueen over MCP or the CLI, right beside the code you are shipping.

Start a 7-day trial for $0More about Cursor

Quick start

Drop the MCP config into your project and Cursor's agent gets Listmonk scheduling as a native tool.

MCP supported
.cursor/mcp.json
{
  "mcpServers": {
    "postqueen": {
      "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY"
    }
  }
}
# Then ask: "Schedule our Listmonk campaigns"

What Cursor can run on Listmonk

Listmonk updates beside your code

Cursor's agent can read the repo and the changelog, then turn them into scheduled Listmonk campaigns over MCP without you leaving the editor.

Windows that fit Listmonk

Tell Cursor when your lists are busiest and it schedules campaigns into that window on Listmonk, day after day, without reminders.

Whole campaigns, scheduled

Cursor drafts the campaign and postqueen delivers it to your Listmonk lists, so subscribers hear from you on a schedule you set once.

Drafts until you are ready

Ask Cursor for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your subscribers on Listmonk until you do.

Three steps to a full queue

Step 1

Discover Listmonk

Cursor calls postqueen to list your connected lists and sees what Listmonk supports, so drafts start from real capabilities, not guesses.

Step 2

Draft with Cursor

Give it the brief. The agent writes Listmonk-shaped campaigns and proposes publish times that match when your subscribers are around.

Step 3

Check and publish

Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Cursor can pull the results after.

What Listmonk allows

Cursor reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.

Campaign formats
Rich HTML, Markdown or plain text
Personalization
Template variables such as subscriber name and attributes
Lists
Public or private, single or double opt-in
Delivery
Your own SMTP servers, multiple configurations supported
Scheduling
Campaigns accept a send date through the API
Hosting
Open source and self-hosted, backed by PostgreSQL
Listmonk

Everything postqueen does on Listmonk

Scheduling, AI drafts, analytics and team roles, in one guide.

Read the Listmonk guide
F.A.Q.

Frequently asked questions

How does Cursor connect Listmonk to postqueen?

Over MCP, registered once in Cursor's own config so the Listmonk tools are there in every session. It also runs commands, so the CLI covers the same Listmonk campaigns when you would rather script them; both use the same API key.

Can Cursor schedule Listmonk campaigns at exact times?

Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the campaigns it creates, keeping your lists active on a steady rhythm.

Will Cursor publish to Listmonk on its own?

Only if you ask it to. Tell it to save drafts and nothing is scheduled: the campaigns wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.

Can one brief cover Listmonk and other channels too?

Yes. postqueen connects 30 channels, so Cursor can turn the same brief into Listmonk campaigns plus adapted versions for every other channel you run.

Does Cursor access cost extra on postqueen?

No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.

What analytics are available for campaigns?

Listmonk records campaign views and link clicks in its own dashboard when tracking is enabled, and that data stays on your server. postqueen keeps the calendar side: which campaigns went out, when, and how they line up with the rest of your content.

Why would a scheduled campaign fail to send?

The usual suspects are an instance that is unreachable from postqueen, revoked API credentials, an SMTP server that is missing or misconfigured in Listmonk, or a campaign pointed at an empty list. postqueen reports the error on the campaign so you can correct it and resend.

Ready to get started?

Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.

Start a 7-day trial for $0See pricing

Seven days free. Cancel in one click from settings.