How to Connect Cursor to WordPress: Cursor MCP Server Setup With InstaMCP

To connect Cursor to WordPress, add the site to Cursor as an MCP server. On an InstaWP site, switch on MCP and click Add to Cursor, or paste a url and an Authorization header into ~/.cursor/mcp.json. Cursor then gets 43 WordPress tools next to your code, so one agent can edit a plugin file, update the page that describes it and check the live result.

On 22 October 2026, InstaWP connected Cursor’s own command-line agent (Cursor CLI 2026.10.19) to a sandbox running InstaMCP, the WordPress MCP server built into InstaWP sites. InstaWP tested both ways in, a site token and an account-wide OAuth sign-in, broke the config five different ways to see what Cursor reports, and made one real code-and-content change on the live site. Every number below comes from that run.

Read the table as two decisions: which connection to make (rows 2 to 5) and which brakes to keep (rows 8 and 10). The rest of this guide takes them in that order.

What can Cursor do once it is connected to WordPress?

Once connected, Cursor can read and change the live WordPress site, not just the files in your editor. Over InstaMCP it creates and edits posts and pages, validates Gutenberg blocks, writes post meta, installs and edits plugins and themes, uploads media and reads the site’s error logs. The point for a Cursor user is that code and site live in one conversation: change a plugin, update the page that explains it, then check the page.

Read the right-hand column before you write your first prompt. Most surprises come from it: the power tools are visible in Cursor’s tool list but refuse to run, and Safe Mode blocks exactly the writes a coding agent wants to make. The site MCP documentation lists every tool.

Should you connect Cursor to one site or to your whole InstaWP account?

Connect one site when you are coding on that site; connect your account when you manage many. InstaWP offers both, and Cursor supports both. Site MCP reaches inside one WordPress install with a token. InstaWP Account MCP signs in once with OAuth and works across the sites in your current team, at the hosting level.

Read the “Reaches” row as the real difference. Site MCP works inside WordPress; Account MCP works on the hosting around it. Many agencies connect both: the account for the overview, and the one site they are coding on. InstaWP explains the split in more depth in Account MCP vs Site MCP.

What do you need before you connect Cursor to WordPress?

You need Cursor, a WordPress site hosted on InstaWP with MCP available, and a few minutes. Cursor’s desktop app and its CLI both support remote MCP servers with headers and OAuth, according to Cursor’s MCP documentation.

• Cursor, the desktop app or the Cursor CLI. This guide was tested on the CLI, version 2026.10.19.
• A WordPress site on InstaWP. Site MCP is available on the Sandbox plan and above. Create a site from scratch or from a template, or use an existing one. A WordPress staging copy of a live site is the safest target (staging is included on Pro and above).
• InstaMCP on the site. It comes with InstaWP sites; the MCP tab switches it on. InstaMCP runs on InstaWP-hosted sites only, so a site hosted elsewhere has to move to InstaWP managed WordPress hosting first.
• For Account MCP only: MCP switched on for your account under Profile, MCP. It is off by default.

Steps 1 to 4 connect one site with a token. The section after them connects your whole account with OAuth. Do whichever you need; they do not depend on each other.

Step 1: How do you switch on MCP for the WordPress site?

Open the site in the InstaWP dashboard, go to Extensions, then MCP, and switch on Enable MCP. The connection URL appears straight away, in the form https://your-site.instawp.site/insta-mcp?t=YOUR_TOKEN, and the client buttons below it are no longer blurred.

Step 2: How do you add the WordPress site to Cursor in one click?

Click Add to Cursor on the MCP tab. The button is a Cursor deep link: your browser hands it to the Cursor app, and Cursor shows its own install dialog for you to approve before anything is added. Nothing is installed by visiting the link alone.

InstaWP decoded the link its dashboard generated for the test site. It is 295 characters long and carries the server name and a base64 copy of the config. The server name is the site’s address turned into a slug, so each site gets its own entry in Cursor instead of overwriting the last one.

cursor://anysphere.cursor-deeplink/mcp/install
  ?name=corner-crumb-instawp-site
  &config=<base64 of the JSON below>

# decoded config
{
  "url": "https://corner-crumb.instawp.site/insta-mcp",
  "headers": { "Authorization": "Bearer YOUR_TOKEN" }
}

Notice two things in that config. The URL has no ?t= query, and the token travels in an Authorization header instead. That keeps the token out of server access logs and out of anything that records URLs. The same block sits under Setup guides for AI clients, then Cursor, with its own Install in Cursor button.

Step 3: How do you add InstaMCP to Cursor’s mcp.json by hand?

Copy the JSON from the Cursor setup guide into ~/.cursor/mcp.json to make the site available in every project, or into .cursor/mcp.json inside one project folder. Cursor merges the two files, and if both use the same server name, the project file wins. Save the file, then restart Cursor or toggle the server in Customize, then MCPs.

{
  "mcpServers": {
    "corner-crumb-instawp-site": {
      "url": "https://corner-crumb.instawp.site/insta-mcp",
      "headers": {
        "Authorization": "Bearer ${env:INSTAWP_SITE_TOKEN}"
      }
    }
  }
}

That version keeps the token out of the file. Cursor resolves ${env:NAME} in the url and headers fields from your environment, as Cursor documents for config interpolation. InstaWP tested it: with INSTAWP_SITE_TOKEN exported, Cursor showed the server as ready; with the variable unset, it showed Error: Connection failed. Export the variable in your shell profile and restart Cursor so the app can see it.

Step 4: How do you check that Cursor can see the WordPress tools?

Open Customize, then MCPs in Cursor and confirm the server is switched on and lists its tools. In the Cursor CLI, cursor-agent mcp list shows each server’s status and cursor-agent mcp list-tools prints the tools. This is what InstaWP’s run printed:

$ cursor-agent mcp list
corner-crumb-instawp-site: ready
# 3.95 s from command to "ready"

$ cursor-agent mcp list-tools corner-crumb-instawp-site
Tools for corner-crumb-instawp-site (43):
- assign_terms_to_content (content_id, taxonomy, term_ids, append)
- create_content (content_type, title, content, status, ...)
- patch_content (content_id, operations, dry_run, create_backup)
- plugin_files (action, plugin, file_path, content, create_backup)
- site_logs (source, lines, level, search)
- validate_blocks (content, render)
# ...37 more

Then give Cursor a read-only first job, so you see it work before it changes anything: “Use the corner-crumb MCP server. List the active plugins and theme, and read the last 50 fatal errors from site_logs.” In InstaWP’s run, plugin_info answered in 0.72 seconds and theme_info in 0.78 seconds.

Cursor decides which tool calls need your approval. By default the agent asks before using an MCP tool. In Cursor 3.6 and later, the default Auto-review run mode lets allowlisted tools run straight away and sends the rest through a classifier, which Cursor’s run modes documentation says is not a security boundary. For a live site, keep Auto-review or Allowlist and do not use Run Everything.

How do you connect Cursor to your whole InstaWP account with OAuth?

Switch on MCP for your account, add https://app.instawp.io/mcp to Cursor, and sign in when Cursor asks. There is no token to copy: Cursor registers itself with InstaWP’s OAuth server, opens the sign-in in your browser and stores the result. InstaWP’s Account MCP docs cover the same flow for other clients.

1. In the InstaWP dashboard, open Profile, then MCP, and switch on Enable MCP for your account. It is disabled by default.
2. Click Add to Cursor, or add {"url": "https://app.instawp.io/mcp"} under a server name such as instawp in mcp.json. No headers are needed.
3. Cursor shows the server as needing sign-in. In the CLI, cursor-agent mcp list printed instawp: requires_authentication, and cursor-agent mcp login instawp opened the sign-in.
4. On the Authorize Cursor screen, choose Read-only or Read & write, then click Authorize. The browser shows “Authorization complete!” and hands control back to Cursor.

Under the hood this is standard MCP OAuth, and both sides advertise it. InstaWP’s server publishes its protected resource metadata, a registration endpoint and PKCE with S256.

Cursor’s CLI registered itself, sent a PKCE challenge and listened on http://localhost:8787/callback, which is the desktop callback Cursor documents. After sign-in, cursor-agent mcp list showed instawp: ready and listed 18 tools on the read-only connection, including list_sites, list_site_plugins with an updates-only filter, list_backups and get_magic_login.

Every app that signs in is listed under Connected apps on the same page, with the date it was authorized and when it was last used, so you can see what has access. To shut every app out at once, switch off Enable MCP for your account: in InstaWP’s test, Cursor’s next request was refused with “MCP access is disabled for this account”.

What does a real Cursor and WordPress workflow look like?

A real workflow changes code and content together and then proves the result on the live page. InstaWP ran one on the test sandbox, a small bakery site with a custom order-ahead plugin. The request: orders now close at 4 pm instead of 6 pm, and the notice should say “4 pm”, not “16:00”. This is the prompt a Cursor user would type:

Use the corner-crumb MCP server.
In corner-crumb-tools/corner-crumb-tools.php, change the order cutoff from 6 pm to 4 pm,
and show the time in the notice as "4 pm" rather than "16:00". Show me the diff first.
Then write the file, read site_logs for fatal errors, update the "Orders close at 6 pm"
sentence on the Order ahead page with patch_content (dry run first), and fetch the page
to confirm both say 4 pm.

InstaWP then made each of those tool calls over the site’s MCP endpoint, the same JSON-RPC requests Cursor’s agent sends once the server is connected. (Running Cursor’s own chat agent needs a Cursor account sign-in, which this test did not use.) The table shows what happened, in order.

Read the third row and the sixth row together. They are the two moments a Cursor user is likely to stop and assume something is broken. The refusal is Safe Mode doing its job, and the stale page is PHP’s OPcache serving compiled code until it checks the file again. Ask Cursor to re-fetch the page after a short wait before it starts “fixing” a change that already worked.

// before
const CCT_CUTOFF_HOUR = 18; // Orders for tomorrow close at 6 pm, site time.
__( 'Orders close at %1$d:00 for next-day pickup. ...' ), CCT_CUTOFF_HOUR,

// after
const CCT_CUTOFF_HOUR = 16; // Orders for tomorrow close at 4 pm, site time.
__( 'Orders close at %1$s for next-day pickup. ...' ),
    gmdate( 'g a', CCT_CUTOFF_HOUR * HOUR_IN_SECONDS ),

The same pattern works for theme files with theme_files, and for new plugins with plugin_operations from a zip. Compare the agent’s code with the WordPress Plugin Handbook before you approve it: nonces, sanitised input and escaped output.

Why does Cursor say “Connection failed” for a WordPress MCP server?

Because Cursor’s CLI uses one message for several different problems. InstaWP broke the config five ways, and Cursor’s CLI printed Error: Connection failed every time. The server’s own response tells them apart, so check that before you change anything.

Read the middle column as the diagnosis. An HTML answer means you are not reaching InstaMCP at all; a JSON 401 means you are, and only the token is wrong. This command reproduces Cursor’s first request and prints the status code:

# expect 200 and application/json; anything else matches a row in the table
$ curl -s -o /dev/null -w "%{http_code} %{content_type}\n" -X POST \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer $INSTAWP_SITE_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}' \
  https://your-site.instawp.site/insta-mcp

Inside the Cursor app, the detail is in the Output panel (Cmd+Shift+U on a Mac, Ctrl+Shift+U on Windows and Linux) under MCP Logs, as Cursor’s MCP help page describes. For a PHP error on the WordPress side, InstaWP’s guide to finding site error logs shows where site_logs reads from.

How do you keep Cursor safe on a live WordPress site?

Point Cursor at a staging copy, keep approvals on in Cursor, and keep InstaMCP’s Safe Mode on except for the one step that needs it. Cursor’s settings decide what the agent may try. InstaMCP’s settings decide what WordPress will accept, even if the agent tries anyway. You want both.

Read the rows as pairs. A user in a hurry can relax any Cursor control from the chat. The InstaWP controls hold whatever the agent decides, because only a site admin or the account owner can change them. InstaWP goes further into the risks in is MCP WordPress integration safe and how to use MCP for WordPress in production.

Is Cursor the best AI client for WordPress, or should you use Claude Code or ChatGPT?

Cursor is the best fit when the work is mostly code you can see, such as a plugin or a theme. The WordPress side is the same in every client: InstaWP lists 14 clients on the MCP tab, and the same site URL works in all of them.

• Cursor suits developers who want to read every file and diff, with the site one tool call away.
• Claude Code is terminal-first and works well with reusable skills. InstaWP shows that style in Claude Code skills for web development and in how to connect Claude to WordPress.
• ChatGPT suits content and site management without an editor. See how to connect ChatGPT to WordPress.

For the protocol itself and other clients, how to connect AI agents to WordPress using MCP and InstaWP’s WordPress MCP guide go deeper, and the WordPress MCP servers comparison covers servers other than InstaMCP. The Model Context Protocol site has the specification.

Connecting Cursor to WordPress: FAQs