Skip to content

WPShout Newsletter

Sign up for news, tips, and insights to help you build better websites.

Newsletter - Top banner

How to Connect Cursor to WordPress With MCP (Developer’s Setup)

Your AI code editor probably writes a real chunk of your code by now. Meanwhile your CMS still lives in a browser tab, and a “quick content change” means leaving the editor to go click through wp-admin.

MCP closes that gap. Hook WordPress up as an MCP server and Cursor’s chat can draft posts, update media metadata in bulk, pull your analytics, and triage comments, all without leaving the editor. The setup is quick, and the plugin behind it is free.

Here’s the developer’s version of the setup: scoped tokens, the config file, seven workflows that are actually worth it, and the guardrails that make giving an AI write access survivable.

Featured graphic for a developer guide to connecting Cursor to WordPress with MCP

Time to get into it.

What MCP actually buys you on WordPress 🧩

The thirty-second version: MCP (Model Context Protocol) is a common language that lets AI clients talk to tools and data sources. WordPress doesn’t speak it natively, which is where Easy MCP AI comes in. It’s a free plugin that turns your site into an MCP server, so any MCP-compatible client (Cursor, Claude, ChatGPT, Gemini, Cline, Manus, n8n) can manage the site through one endpoint. Disclosure, once: it’s built by ThemeIsle, the family WPShout belongs to.

The scope is bigger than “draft a post.” The plugin ships 280+ tools covering posts, pages, media, taxonomies, comments, users, menus, CPTs, revisions, blocks and settings, plus plugin integrations for WooCommerce, ACF, The Events Calendar, BuddyPress, six SEO plugins, Redirection, Contact Form 7 and Site Kit by Google, and data integrations for Google Analytics 4, Search Console, Semrush, SE Ranking, DataForSEO and Ahrefs. Each plugin integration group starts off until an admin switches it on under Easy MCP AI > Tools > Abilities, and each data integration loads once its credentials are saved under Easy MCP AI > Tools > External data or defined as wp-config.php constants or environment variables (Ahrefs loads once an admin opts in). On WordPress 6.9 and newer it also exposes the WordPress Abilities you enable under Easy MCP AI > Tools > Abilities: a fresh install starts with the abilities their plugins explicitly mark non-destructive already enabled (WooCommerce’s and a few others are excluded), and abilities added later stay off until you enable them.

OAuth or token: pick the route that matches your client

There are two ways in, and the right one depends on the client:

  • OAuth 2.1 one-click for compatible clients, Cursor included. The plugin ships a full authorization server (PKCE, refresh-token rotation, Dynamic Client Registration), and its connect card on the Dashboard and under Connections has an “Add to Cursor (1-click)” button that opens Cursor with the server pre-filled: confirm in Cursor, sign in to WordPress, choose the access on the consent screen, and click “Approve & Continue”.
  • Bearer token for clients and setups where OAuth is not an option, such as n8n and scripts. You create a token in wp-admin, paste it into the client’s MCP config, and that’s the whole handshake.

Tokens aren’t all-or-nothing strings, which is the part that matters. The token form offers Full access, Read-only and Custom access levels, and the same scoped access applies to OAuth grants; the raw token is only stored as a SHA-256 hash, every tool call passes a WordPress capability check, and a per-token rate limit you set (1 to 1000 requests a minute, 120 a minute by default on a new install) keeps a runaway agent from speed-running your database.

“Doesn’t the REST API already do this?”

Yes, and if you’re happy writing fetch calls and auth plumbing for every automation, keep doing that. The difference is who writes the integration. With REST you build and maintain the client, the auth, the error handling, and the permission model yourself, per script. With MCP the client is the AI you already use, the tools are pre-built and typed, and auth, scoping, and logging ship with the plugin. You’re trading a pile of bespoke scripts for a one-click connection, or at most one config file and a token.

REST still wins for hard-coded, high-frequency production integrations where you want zero LLM in the loop. MCP wins for the fuzzy, judgment-shaped work (draft this, summarize that, clean up the other thing) that scripts are terrible at.

The setup, in four steps ⚙️

1. Install Easy MCP AI

It’s on WordPress.org (30,000+ active installs, rated 98 out of 100 from 16 ratings). Requires WordPress 6.0+ and PHP 7.4. Install it from the Plugins screen in wp-admin, activate, and a new Easy MCP AI menu appears. No Node.js, no external proxy, no second subscription. The plugin itself is free; a few optional SEO-data integrations (Semrush, SE Ranking, DataforSEO) need those vendors’ own paid accounts, while the Ahrefs Domain Rating lookup runs on a free Ahrefs API key.

A word on what the AI can and can’t see once it’s connected. Token scopes map onto ordinary WordPress capabilities, and every single tool call is checked against them. A read-only token can list, query, and report on anything your user role can see, but every write attempt gets rejected. That makes read-only genuinely useful for exploration (traffic questions, content audits, “what’s broken”) while keeping write a deliberate, later grant. Nothing is silently elevated, and while the Audit log is on (it is by default) it records every MCP tool call.

2. Connect Cursor with one click (OAuth)

Open Easy MCP AI > Dashboard (the same connect card sits under Connections), pick Cursor in the “Connect your AI client” card, and click “Add to Cursor (1-click)”. Cursor opens with the server pre-filled; confirm there, sign in to WordPress, choose the access on the consent screen, and click “Approve & Continue”. No token, no config file. One requirement on a live site: OAuth sign-in needs HTTPS.

Easy MCP AI connect card for Cursor with the Add to Cursor (1-click) button and the API token alternative link
The connect card’s Cursor step: one click opens Cursor with the server pre-filled.

3. Or connect with a scoped API token

Prefer a token, or a setup OAuth can’t reach? Expand “Use an API token instead” on the same card and it shows the snippet for ~/.cursor/mcp.json, your site URL already filled in, with Bearer YOUR_API_TOKEN as the placeholder. Create the token under Easy MCP AI > Connections > API tokens > Create token: the form starts on Full access with a 30-day expiry (7, 60 or 90 days, Never, or a custom date), so a cautious first run picks Read-only. Name the token after the client using it (“cursor-laptop”), so the Audit log reads clearly later.

Easy MCP AI Create token panel with name, WordPress user, access level cards and expiry options
The Create token panel: pick the access level and expiry before creating.
{
  "mcpServers": {
    "wordpress": {
      "url": "https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_TOKEN" }
    }
  }
}Code language: JSON / JSON with Comments (json)

Paste the snippet into ~/.cursor/mcp.json, replace YOUR_API_TOKEN with the token you just created, then restart Cursor and open the AI panel: your WordPress site is now a tool it can call.

4. Smoke-test with three prompts

Verify the loop before you trust it with real work:

  1. “List my five most recent draft posts.” (read path)
  2. “What keywords does my homepage rank for, and what are the click counts?” (Search Console integration, if connected)
  3. “Create a draft post titled ‘MCP smoke test’ with one paragraph about WordPress.” (write path, if the access you granted allows it)

All three should come back with real data from your site. If prompt two says the integration isn’t configured, that’s the Search Console credentials under Easy MCP AI > Tools > External data, not a Cursor problem.

Seven workflows worth the wiring 🔧

Once the plumbing works, these are the jobs that actually pay it off:

  • Bulk SEO meta sweep. “Find every published post missing a meta description and draft one for each.” That’s Yoast/Rank Math/AIOSEO/SEOPress/Slim SEO/The SEO Framework metadata, readable and writable through the plugin, once the SEO plugin’s integration group is on: every integration group starts off until an admin switches it on under Easy MCP AI > Tools > Abilities.
  • Media alt-text batch. “List media items with empty alt text and write descriptive alt text for each.” Easy MCP AI hands the AI each image’s URL and metadata as text; the client has to open the image itself, so this pays off with a client that can fetch and view images, and the results still deserve a review pass.
  • Comment triage. “Show me pending comments, flag the obvious spam, and summarize the rest.” Approve from the chat, or keep it read-only and just get the summary. (If agentic plugins are your thing generally, the WordPress on autopilot piece maps the territory.)
  • WooCommerce morning report. “Show me today’s orders and their total revenue.” Sales, top sellers, and revenue reports are all tool calls, once the WooCommerce group is switched on under Easy MCP AI > Tools > Abilities; like every integration group, it starts off.
  • Analytics questions without the GA4 tab. “Which pages got the most traffic this week?” or “Which queries dropped in clicks?” GA4 and Search Console, answered in the editor, once the credentials are saved under Easy MCP AI > Tools > External data or defined as wp-config.php constants or environment variables.
  • Find-and-replace with a brain. “Find posts that mention our old pricing page and list them with links.” The plugin has content find-and-replace built in, and the AI supplies the judgment about which hits actually need editing.
  • Custom post type wrangling. Portfolios, listings, courses, reviews: if it’s a CPT registered with show_in_rest=true, the same CRUD tools apply. “Create three draft case studies in our portfolio CPT from these bullet points” is a legitimate prompt.

Notice the pattern: none of these is “write my blog for me.” The ROI is the boring admin you’d otherwise do by clicking around wp-admin for an hour.

One practical note on batch jobs: the per-token rate limit defaults to 120 requests a minute on a new install, and the site owner can set it anywhere from 1 to 1000. A big alt-text batch is fine, but it’s a paced job, not a burst. For heavy batches, ask the client to work in chunks and check the audit log between them.

The trust layer: guardrails that make this survivable 🛡️

Handing an AI write access to a production site is a real decision, not a vibe. The plugin’s answer is visibility:

  • Audit log. While it’s on (it is by default), every MCP tool call is recorded with the credential used, the tool, redacted arguments, the result status or error, the duration, and the client IP, in a searchable activity log. “What did the AI actually do?” is a query, not a guess. The on/off switch and retention live under Easy MCP AI > Settings > Logging & history.
  • Change history. Changes made through MCP get before/after snapshots you can diff (on by default on new installs, kept 30 days), under Easy MCP AI > Activity > Change history; retention is set under Easy MCP AI > Settings > Logging & history.
  • Scoped tokens. Read-only for exploration, write per content type for automation, revoked in one click when a client leaves the project.
  • Rate limits and IP whitelisting for the endpoint, configurable in settings.

The habit to build: read-only first, watch the audit log for a week, then grant write scopes deliberately. The plugin makes that progression cheap, so there’s no excuse for skipping it.

Where this doesn’t fit ⚠️

Honest edges, so nobody discovers them in production:

  • It’s a young plugin. 30,000+ active installs and a 98 out of 100 rating, but from 16 ratings. That’s enthusiasm from a small sample, not a long track record. Test on staging first, with staging’s own connection: API keys are bound to the host that issued them, so a key created on production is refused on a staging copy.
  • It’s not a hosted service. Your AI talks to your site directly. If the site is behind basic auth or unreachable from the client, nothing works until that’s fixed.
  • Third-party SEO data costs extra. Semrush, SE Ranking, and DataforSEO need those vendors’ accounts. The plugin itself and the GA4/GSC integrations are free.
  • WordPress core’s built-in AI client is a different thing. Its connectors feature has its own model (there’s a developer’s guide to the AI client on this site). Easy MCP AI is the plugin route, and it works today on WordPress 6.0+.

Last word 💬

Connecting Cursor to WordPress with MCP is a quick setup that takes a lot of routine wp-admin clicking off your plate: one-click OAuth (or a token in one config file), scoped access, and an Audit log of every MCP tool call while it’s on. Start read-only, prove the loop, then hand over the boring work one scope at a time.

Have you wired an AI client into a production WordPress site? What did you trust it with first, and what did you keep read-only?

Yay! 🎉 You made it to the end of the article!
Team WPShout
Share:

0 Comments
Most Voted
Newest Oldest