Skip to content

How to Connect Cursor to WordPress ​

Connecting Cursor to your WordPress site puts your content next to your code: the AI in your editor can read and update posts and pages, check site settings, or wire up content while you build a theme or plugin. Easy MCP AI runs the MCP server inside WordPress, and Cursor connects to it in one click.

In this article

Prerequisites ​

  • A WordPress site served over HTTPS with Easy MCP AI installed and activated (see the installation guide).
  • Pretty permalinks enabled (Settings > Permalinks set to anything other than "Plain").
  • The Cursor editor installed and signed in.

You'll need your site's MCP endpoint URL, which is always your domain followed by /wp-json/easy-mcp-ai/v1/mcp:

https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp

You can copy it from Easy MCP AI > Dashboard in your WordPress admin: click Connect an AI client, choose your client, and copy the URL shown in the Add this site step.

Screenshot: The Easy MCP AI Dashboard with the Connect an AI client card open at the Add this site step, showing the MCP endpoint URL and its Copy button

  1. Go to Easy MCP AI > Dashboard, click Connect an AI client and choose Cursor.
  2. Click Add to Cursor (1-click). The link opens the Cursor desktop app directly with your WordPress server pre-filled.
  3. Confirm to add the server. Cursor uses OAuth: your browser opens a WordPress authorization page, you choose an access level (Read-only, Full access or Custom) and approve it, and the connection is ready. No token needed.

Cursor's install prompt showing the pre-filled WordPress MCP server

See Managing OAuth Access in Easy MCP AI for access levels, grant management, and what to do after changing your site address.

Option 2: Manual Configuration with an API Token ​

If you prefer explicit credentials, or manage your MCP servers in a dotfile:

  1. Create an API token in Easy MCP AI > Connections (API tokens tab) and copy it.
  2. Add the server to ~/.cursor/mcp.json, replacing the URL with your endpoint and YOUR_API_TOKEN with your token:
json
{
  "mcpServers": {
    "wordpress": {
      "url": "https://yoursite.com/wp-json/easy-mcp-ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
  1. Save the file. Cursor picks up the new server; if it doesn't appear, restart Cursor.

Verify the Connection ​

Back on the Easy MCP AI Dashboard, the top of the page shows Connected: 1 OAuth grant (a higher number if you already had other connections). Once your AI client calls a tool, the call appears under Recent activity in the Dashboard sidebar.

Open the Customize panel in Cursor's sidebar. The wordpress server shows as connected with its tools listed.

Cursor's MCP settings showing the wordpress server active with its tool list

Then ask the agent something that touches your site:

Which are the five most recent posts on my WordPress site, and which of them are still drafts?

Cursor asks for approval the first time it runs a WordPress tool.

What You Can Do Once Connected ​

Easy MCP AI exposes your site's capabilities as MCP tools, organized by area: posts, pages, media, comments, categories and tags, menus, custom post types, blocks, revisions, users, plugins, themes, site settings, and search. Integrations such as WooCommerce and SEO data sources are included when available. In an editor, that shines for development-adjacent tasks:

Create a draft page called "Pricing" using the block markup in the file I have open.

List the active plugins on my site and their versions.

Check which template the blog page uses and show me its content.

Control What Cursor Can Access ​

The connection acts as the WordPress user who approved it (or the token's assigned user), so WordPress roles apply as usual. For a development setup, consider a dedicated token limited to the tools you need. Site-wide guardrails (globally disabled tools, rate limits, forced drafts, audit log) apply on top. See Creating and Managing API Tokens for details.

Security ​

If you identify a potential security vulnerability in this plugin, please disclose it responsibly. Follow the protocols on the Themeisle Security Page.

Was this helpful?