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

Automate WordPress with Cursor

Schedule WordPress articles 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 WordPress 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 WordPress articles"

What Cursor can run on WordPress

WordPress updates beside your code

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

Windows that fit WordPress

Tell Cursor when your sites are busiest and it schedules articles into that window on WordPress, day after day, without reminders.

Long-form arrives intact

Cursor hands postqueen the full draft, formatting included, and it lands on your WordPress sites as complete articles, ready for readers.

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 readers on WordPress until you do.

Three steps to a full queue

Step 1

Discover WordPress

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

Step 2

Draft with Cursor

Give it the brief. The agent writes WordPress-shaped articles and proposes publish times that match when your readers 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 WordPress allows

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

Post format
Title, HTML body, excerpt and featured image
Taxonomy
Unlimited categories and tags
Statuses
Draft, pending review, private, scheduled, published
REST API
Built into WordPress core since version 4.7
Authentication
Application passwords, standard since WordPress 5.6
Media
Images, video and audio through the media library
WordPress

Everything postqueen does on WordPress

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

Read the WordPress guide
F.A.Q.

Frequently asked questions

How does Cursor connect WordPress to postqueen?

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

Can Cursor schedule WordPress articles at exact times?

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

Will Cursor publish to WordPress on its own?

Only if you ask it to. Tell it to save drafts and nothing is scheduled: the articles 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 WordPress and other channels too?

Yes. postqueen connects 30 channels, so Cursor can turn the same brief into WordPress articles 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 do I get for WordPress posts?

WordPress core does not ship analytics, so most sites rely on their web analytics tool or a stats plugin, and those keep working exactly as before. postqueen tracks the publishing side: what went out, to which site, and what is queued next across all your channels.

Why would a scheduled WordPress post fail?

Typical causes are a security plugin or firewall blocking the REST API, a revoked application password, a changed site URL, or a connected user whose role cannot publish. postqueen surfaces the site's error message on the post so you can fix the cause and retry quickly.

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.