Cursor is an AI code editor, and WordPress work in Cursor usually means two things at once: theme or plugin code in the editor, and a live site to act on. Connecting Cursor to WordPress through MCP covers the second part: the agent can then read the site, change content and settings, and check its own work, without leaving the editor. This guide shows the setup and the errors that come up most often.
Can Cursor work on a WordPress site?
Yes. With a WordPress MCP connection configured, Cursor’s agent can create and edit posts and pages, build Elementor and Bricks layouts, manage plugins, query the database and run PHP on the site, alongside the code it edits in your repository. With Novamira the connection is direct between Cursor and your site.
Which connection method should you choose?
| Route | Setup | Best for |
|---|---|---|
| MCP with OAuth | One block in mcp.json, sign in from the browser |
Most setups; the default for Cursor |
| Novamira CLI | One install, one login per site | Cursor’s terminal agent, work on several sites |
| Custom MCP server on the REST API | You build and host it | Teams with specific needs and time to maintain code |
For Cursor the MCP route is the natural one, because Cursor reads MCP servers from a JSON config that can live in the project itself: the connection travels with the repository, and every teammate who opens the project gets it. The Novamira CLI is an alternative when you drive Cursor’s agent from the terminal across many sites. A custom server on the REST API remains the build-it-yourself option, limited to what the REST API exposes.
What do you need before you start?
- A WordPress site on HTTPS with the Novamira plugin active, free from the download page.
- An administrator account on the site.
- Cursor installed, with MCP enabled in its settings.
How to add a WordPress MCP server to Cursor
Add this to your mcp.json, global at ~/.cursor/mcp.json or per project at .cursor/mcp.json:
{
"mcpServers": {
"novamira-your-site": {
"url": "https://your-site.com/wp-json/mcp/novamira-oauth"
}
}
}Reload Cursor, approve the sign-in from your WordPress login when the browser opens, and the site’s abilities appear among the agent’s tools. The Novamira > Configuration page in your WordPress admin generates this block with your real site URL, ready to copy. Authorizations are listed under Novamira > Manage Connections, where revoking takes effect immediately.
The per-project file is worth preferring when the project is the site: the repo then declares its own WordPress connection, the same way it declares its dependencies.
How to use Cursor with the Novamira CLI
For terminal-driven work, install the Novamira CLI (requires Novamira 1.11.0 or later on the site) and connect the site once with a browser sign-in; the CLI keeps a profile per site and reconnects on its own when a grant expires. Cursor’s agent can then run it like any other command-line tool.
Watch it in action
This independent walkthrough by Paul Charlton at WPTuts covers connecting Cursor, among other agents, to WordPress:
A workflow that holds up
The pattern that works in Cursor: code lives in git, the site connection points where mistakes are cheap, and your own deploy process moves reviewed work onward. Novamira is recommended for staging environments with backups, and Read Mode in Novamira Pro covers read-only inspection on live sites. The Claude Code guide walks through this in more detail.
Common errors and how to fix them
The server never appears in Cursor’s tools. Check the JSON for syntax errors and the file location (~/.cursor/mcp.json or .cursor/mcp.json in the project root), then reload Cursor.
The sign-in never completes. OAuth requires HTTPS, and some hosts filter traffic from cloud AI providers; the docs cover what to do when your host or a firewall blocks the connection.
The site runs locally. Use the mcp-remote bridge shown on the Novamira > Configuration page, which runs the browser sign-in on the client’s behalf.
A tool call is refused. Check which features are enabled under Novamira > Features, and whether Read Mode is active on that site.
Next steps
Point Cursor at a staging copy and give it a task that mixes both sides of its job: build a template in code, fill it with real content through the site connection, and check the rendered result. The tools page lists every ability it can call.