Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTo connect Cursor to WordPress with MCP, first choose the server that matches your project: WordPress.com for eligible hosted accounts, the WordPress MCP Adapter for local or self-hosted site development, the WordPress.org server for Plugin Directory work, or WordPress Studio MCP for sites managed in Studio. Then add that server to Cursor, authorize or configure it, and verify the connection with a read-only request.
Choose the WordPress MCP route for your task
MCP, or Model Context Protocol, connects Cursor to external tools and data sources so its Agent can call the tools a server exposes. Cursor supports both hosted servers and local command-based servers. These WordPress options are related, but they are not interchangeable.
As an Amazon Associate I earn from qualifying purchases.
| Route | Best for | Where it runs and access notes |
|---|---|---|
| WordPress.com MCP Server | Working with eligible WordPress.com sites | A hosted endpoint, https://public-api.wordpress.com/wpcom/v2/mcp/v1. Enable MCP in account settings and authorize through a browser. |
| WordPress MCP Adapter | Developing against a local or self-hosted WordPress site | Exposes WordPress abilities as MCP tools. The documented Cursor examples use either a local stdio command or an HTTP arrangement through a local bridge. |
| WordPress.org MCP Server | Plugin Directory tasks such as checking guidelines, validating readmes, checking submission status, or submitting a plugin | Run with npx -y @wporg/mcp; the setup flow authorizes and configures supported clients, including Cursor. |
| WordPress Studio MCP | Creating, starting, stopping, or interacting with local sites managed by Studio | Studio provides a generated configuration from Settings → MCP for use in Cursor. |
Set up the WordPress.com hosted connection
This is the most direct route when you want Cursor to work with an eligible WordPress.com account. The WordPress.com documentation, last updated September 21, 2026, says MCP is available on paid WordPress.com plans; free sites have access for the first 30 days after creation. It also documents access for self-hosted sites connected through Jetpack with a Jetpack AI or Jetpack Complete plan. Check the current WordPress.com MCP documentation if your account or plan differs.
- In WordPress.com account settings, enable MCP.
- In a browser, open Cursor’s Plugin Directory, search for “WordPress.com,” and select “Add to Cursor.” Cursor should open its MCP settings with the server configuration.
- Select Install, then complete the browser authorization for the WordPress.com account.
- Confirm the server appears enabled in Cursor’s MCP settings. The hosted endpoint documented for manual configuration is
https://public-api.wordpress.com/wpcom/v2/mcp/v1.
The connection uses OAuth 2.1 with browser authorization. WordPress.com documents PKCE, dynamic client registration, token rotation, and revocation through the account’s Connected Apps settings. If you configure another MCP-enabled client manually, Cursor’s documentation describes remote servers using a URL in MCP configuration.
#1 Best Overall
Connect a local or self-hosted site with the WordPress MCP Adapter
Use the Adapter when Cursor needs tools for developing against a WordPress site rather than managing a WordPress.com account or handling Plugin Directory submissions. The official example offers two patterns: run the site’s WordPress command locally over stdio, or use a bridge process that connects to the site’s MCP endpoint over HTTP.
- In Cursor, open Settings → Cursor Settings → Tools and MCP, then choose Add Custom MCP to open
mcp.json. - Add the Adapter server definition that matches your environment. For the local stdio pattern, the configuration runs
wpwith the local site path,mcp-adapter serve, the server name, and the WordPress user. For the HTTP pattern, it runsnpx -y @automattic/mcp-wordpress-remote@latestand supplies the site endpoint, username, and application password as environment variables. - Replace example paths, endpoints, usernames, and credentials with values from your own development environment. Save the configuration, return to Tools and MCP, and enable the server.
The Adapter’s official setup example is illustrative, not a source of credentials for your site. Keep live secrets out of shared project configuration. Cursor documents environment-variable interpolation for configuration, which can help avoid writing credentials directly into the JSON file.
Choose project or personal configuration
.cursor/mcp.jsonis the project-level location Cursor documents for a team-shared server configuration.~/.cursor/mcp.jsonis the global location for a personal configuration available across projects.
Cursor merges the project and global files. If both define a server with the same name, the project-level definition takes priority. Avoid placing personal credentials in a project file that will be shared.
Set up the WordPress.org server for Plugin Directory work
The WordPress.org MCP server is for Plugin Directory workflows, not general editing of a WordPress site. Its tools cover plugin guidelines, readme validation, submission status, and plugin submission.
- Run
npx -y @wporg/mcpin a terminal. - Follow the browser authorization flow. The setup process creates an application password and detects or configures supported clients, including Cursor.
- Confirm the server is configured in Cursor before using its Plugin Directory tools.
Follow the WordPress.org Plugin Directory handbook for manual configuration and authorization details. It states that an account can have only one MCP application password at a time; authorizing again revokes the previous password. Protect the credential accordingly.
Connect WordPress Studio’s local MCP server
Choose this route when your local WordPress sites are managed by Studio and you want an agent to create, start, stop, or interact with them.
- In Studio, open Settings → MCP.
- Copy the generated JSON configuration. Studio’s documented example invokes the
studiocommand withmcpas its argument. - Add the configuration to Cursor’s project file,
.cursor/mcp.json, or global file,~/.cursor/mcp.json. - Enable the server in Cursor’s MCP settings.
See the WordPress Studio MCP instructions for the generated configuration and supported setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Verify the connection safely
Before asking an agent to change content or settings, confirm that Cursor has initialized the server and can retrieve a basic, read-only fact.
- Open Cursor’s MCP settings and check that the intended server is listed and enabled.
- Ask the Agent for basic site information or another low-impact fact available through that server’s tools. The Adapter example demonstrates requesting site information.
- Confirm the response is from the intended site or service before attempting any write operation.
Troubleshoot a connection that does not work
WordPress.com authorization or missing tools
- Check that MCP is enabled in the account and that the account or connected Jetpack setup meets the documented eligibility requirements.
- Confirm the server URL is correct if you entered it manually, and complete the browser authorization flow.
- Check the account’s Connected Apps settings to see whether the client is connected.
- If account tools or site MCP access were disabled, reconnect so Cursor refreshes its available tool list. Restart Cursor if needed.
Cursor reports an MCP server error
- Open Cursor’s Output panel and select MCP Logs. Cursor says these logs show server initialization, tool calls, and error messages.
- Look for connection failures, authentication errors, or a server process that stopped unexpectedly.
- Check that local command paths, site endpoints, and required environment variables match your setup.
- Toggle the server off and on from Cursor’s Customize interface while troubleshooting.
Cursor’s MCP integrations documentation explains its configuration options and log access. Its concise description is: “MCP (Model Context Protocol) connects Cursor to external tools and data sources.”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
