PlugPress

Connect Cursor to WordPress

Cursor’s AI can work on your WordPress site straight from the editor’s chat — reading content, writing posts, editing pages. Setup is one MCP server config that Saddle generates for you.

What do I need before connecting?

How do I connect Cursor to my WordPress site?

Step 1: Open the connect wizard

In your WordPress dashboard, go to Saddle → Connections, click Connect an app, and choose Cursor.

Saddle connect wizard in WordPress showing the Choose app step with Claude, ChatGPT, Claude Code, Cursor, Gemini CLI, VS Code and Any MCP app

Step 2: Copy the generated config

Saddle setup step for Cursor showing the mcp.json configuration with the WordPress MCP server URL and Authorization header

It looks like this — yours has your real address and key:

{
  "mcpServers": {
    "saddle-your-site": {
      "url": "https://your-site.com/wp-json/saddle/v1/mcp",
      "headers": {
        "Authorization": "Basic PASTE-YOUR-KEY-HERE"
      }
    }
  }
}

Copy it before closing the wizard. The key appears this once, and backing out early revokes it. Lost it? Use Rotate key on the app’s row.

Step 3: Add it to Cursor

Open Settings → MCP → Add new server and paste the config — or save it as .cursor/mcp.json in your project to share the connection with that workspace.

If you commit that file to a repository, remember the key is in it. For anything shared, prefer Cursor’s global settings.

How do I know it worked?

Open Cursor’s chat and ask:

What can you see on my WordPress site?

It should report your site name, WordPress version, and content counts, and the app appears in Saddle → Connections.

What can Cursor do on my site?

Only what you allow on the Permissions screen — sites start read-only, and deletions always require a preview-and-confirm approval.

It didn’t connect — what now?

A stripped Authorization header is the most common cause of a rejected connection, and it has a one-click fix. Open Saddle → Connections → Connection details & health and click Test the endpoint, then see Troubleshooting and FAQ.

FAQ

Global settings or .cursor/mcp.json?

Global settings if the site connection is yours; the project file if a whole workspace should share it. Don’t commit the project file to a public repository — it contains a working key.

Can I connect several sites?

Yes — add more entries under mcpServers. Each site’s wizard generates its own distinct name.