---
title: "Connect Cursor to WordPress"
url: "https://plugpress.co/docs/connect-cursor-to-wordpress.md"
canonical: "https://plugpress.co/docs/connect-cursor-to-wordpress/"
published: "2026-07-28"
modified: "2026-08-01"
author: "Fahim"
description: "Connect the Cursor editor to your WordPress site with Saddle. Add one generated MCP config and work on posts and pages from Cursor's chat window."
tags:
  - "Saddle"
---

# 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?

- A WordPress site on **HTTPS** with the [Saddle plugin](/docs/what-is-saddle/) installed and activated.
- The [Cursor](https://cursor.com) editor.

## 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](https://plugpress.co/wp-content/uploads/2026/07/saddle-connect-wizard-choose-app.png)

### 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](https://plugpress.co/wp-content/uploads/2026/07/saddle-connect-cursor-setup.png)

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](/docs/permissions-access-levels/) screen — sites start read-only, and deletions always require a [preview-and-confirm approval](/docs/safe-deletions/).

## 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](/docs/troubleshooting/).

## 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.

## Related guides

- [Getting started: connect your first AI app](/docs/getting-started/)
- [Permissions and access levels](/docs/permissions-access-levels/)
- [Editing content and design with AI](/docs/editing-content-and-design/)
- [Troubleshooting and FAQ](/docs/troubleshooting/)