Recommended Free Tools
Choose the connection based on where WordPress runs: WordPress.com uses its hosted MCP service and browser-based OAuth, while a self-hosted site uses the WordPress MCP Adapter. For local development, connect through WP-CLI over STDIO; for an agent that must reach a remote site, use the adapter’s HTTP route with deliberate authentication.
Choose the right WordPress MCP route
There is no single endpoint that works for every WordPress installation. First identify whether your site is hosted by WordPress.com or self-hosted, then choose the matching service.
As an Amazon Associate I earn from qualifying purchases.
| Site and use case | Server and endpoint | Transport and access |
|---|---|---|
| WordPress.com hosted site | https://public-api.wordpress.com/wpcom/v2/mcp/v1 | WordPress.com-hosted service; browser-based OAuth 2.1 authorization. MCP is available on paid plans; free sites have access during their first 30 days, according to WordPress.com’s developer documentation. |
| Self-hosted WordPress connected through Jetpack | Same WordPress.com hosted endpoint; there is no separate Jetpack MCP endpoint. | WordPress.com documents this for sites with a Jetpack AI or Jetpack Complete plan. See its MCP documentation. |
| Self-hosted site, local agent and local development environment | WordPress MCP Adapter default server: /wp-json/mcp/mcp-adapter-default-server. WP-CLI serves it over STDIO. |
Run the agent and site locally; configure WP-CLI and choose a WordPress user whose capabilities fit the intended work. |
| Self-hosted site, remote agent or HTTP connection | Adapter default server at https://your-site.com/wp-json/mcp/mcp-adapter-default-server for a publicly reachable HTTPS site. |
HTTP requires endpoint reachability and configured authentication; the documented proxy option uses Node.js. |
| WordPress.org plugin submission and review tasks | Separate service; the handbook’s quick setup is npx -y @wporg/mcp. |
For plugin preparation, readme validation, review status and submission workflows—not general control of a WordPress site. See the WordPress.org plugin handbook. |
The self-hosted adapter documentation identifies WordPress 6.9 and PHP 7.4 as minimum requirements. Check the current Learn WordPress adapter lesson and the adapter’s GitHub Releases for current requirements and installation instructions.
Connect a WordPress.com site
- Check eligibility and enable MCP. In your WordPress.com account settings, enable MCP access. The current plan and access-window terms are described in the WordPress.com Developer Documentation, updated September 21, 2026.
- Add the hosted endpoint to your MCP client. Use
https://public-api.wordpress.com/wpcom/v2/mcp/v1. WordPress.com documents support for MCP-capable clients including Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor and Codex; the configuration method differs by client. - Authorize in your browser. The hosted service uses OAuth 2.1. WordPress.com’s documentation describes PKCE, dynamic client registration, token rotation and no client secrets as parts of its flow. Follow the authorization prompt opened by your client.
- For Codex, add and log in to the server. The documented example is
codex mcp add wpcom-mcp --url https://public-api.wordpress.com/wpcom/v2/mcp/v1. Codex can initiate OAuth automatically; for manual login, the documented command iscodex mcp login wpcom-mcp. If either command fails, check the current Codex documentation because client commands and interfaces can change. - Revoke access if needed. In WordPress.com, open Security → Connected Apps and disconnect the client.
Connect a self-hosted site locally with WP-CLI
When both the coding agent and WordPress development site run on the same machine, the documented straightforward choice is STDIO via WP-CLI. The WordPress Developer Blog calls STDIO the most straightforward connection for local WordPress development environments in its MCP Adapter tutorial, published February 4, 2026. This route avoids making the site externally reachable.
- Install and activate the MCP Adapter. Get the plugin from the project’s GitHub Releases, and confirm your WordPress and PHP versions meet the current adapter requirements.
- Check WP-CLI and the site path. WP-CLI must be installed, and you need the local path to the WordPress installation.
- Configure the MCP client to run WP-CLI. Use command
wpand arguments formcp-adapter serve, the site path, server namemcp-adapter-default-server, and the WordPress user to run as. The precise configuration-file format varies by client; use the client’s current instructions and the Learn WordPress lesson for the setup example. - Choose the WordPress user deliberately. The user’s capabilities affect which operations the agent can perform. Use an account with only the access appropriate to the work.
Connect a self-hosted site over HTTP
HTTP is appropriate when the agent cannot use local STDIO but can reach the site—for example, when an agent runs remotely. The adapter endpoint for a public HTTPS site is https://your-site.com/wp-json/mcp/mcp-adapter-default-server; replace the example host with your own site’s domain.
Use the documented remote proxy
The WordPress Developer Blog describes a Node.js proxy using @automattic/mcp-wordpress-remote. Configure WP_API_URL to point to the site’s MCP endpoint and supply WordPress authentication through environment entries. The documented choices include WordPress application passwords or custom OAuth. Treat application passwords as credentials: do not put them in source-controlled configuration, and use the current proxy and client instructions for the exact configuration syntax.
Give a remote agent temporary access to a local site
A remote agent normally cannot reach a site available only on your computer. The Learn WordPress lesson describes tunneling the local site to obtain a temporary public URL, then using that URL as the HTTP endpoint. A tunnel changes the site’s exposure: use one only when the remote agent needs access, and review the tunnel’s access controls.
Account for reverse proxies
For a reverse proxy that terminates HTTPS, the Learn WordPress lesson says the adapter needs no special configuration beyond standard WordPress REST API setup. Configure the proxy to preserve the Host header and forward the full /wp-json/mcp/ path.
Understand what the agent can do
The MCP Adapter connects the WordPress Abilities API to MCP. Its default server offers tools to discover abilities, retrieve information about an ability and execute abilities. Connecting a client does not grant automatic access to every WordPress feature.
- Abilities must be exposed. The adapter project says WordPress abilities are private by default; an ability must opt in through its metadata to be exposed.
- Authorization is checked. The adapter documents authentication per server transport and permission checks per ability. For local STDIO, access is shaped by the selected WordPress user’s capabilities. For HTTP, configure authentication deliberately and follow current adapter and client guidance.
- Review the client’s data handling too. WordPress.com support documentation says MCP tool data is not used to train AI models and is used as part of the original request. Your organization’s data requirements and the AI client’s own policies still apply.
For implementation details, see the adapter project’s GitHub repository and its WordPress Developer Blog tutorial.
Quick Recap
Best Value
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
Troubleshoot a connection that fails
- Service is missing: Enable MCP in WordPress.com account settings, or check that the MCP Adapter is installed and active on the self-hosted site.
- Endpoint is rejected: Verify that you used the WordPress.com hosted endpoint for a WordPress.com connection, or the self-hosted site’s
/wp-json/mcp/mcp-adapter-default-serverroute for the adapter. Do not swap the two. - Local STDIO does not start: Check that WP-CLI is installed, the WordPress path is correct, the server name is
mcp-adapter-default-server, and the selected user exists and can access the site. - HTTP cannot connect: Check that the endpoint is reachable, the Node.js proxy is configured if you use that route, and authentication credentials are valid. For reverse proxies, verify the
Hostheader and REST path forwarding. - WordPress.com tools are unavailable: Complete the browser OAuth flow and inspect Security → Connected Apps. If tools have been changed or disabled, restart the client so it refreshes the tool list.
- You are working on a plugin submission: Use the separate WordPress.org plugin MCP service and its handbook instructions for troubleshooting and credential revocation; it is not the site adapter.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
