Letting Codex manage a WordPress site? Connect through Jetpack's MCP instead of handing it full WP-CLI

#What changed

Self-hosted WordPress sites connected through Jetpack can now be worked on from ChatGPT or Codex. Jetpack doesn't run a separate server: it links your site to the WordPress.com MCP server, the same one WordPress.com sites use. WordPress developer Brian Coords (@briancoords) still prefers WP-CLI plus the WordPress Agent Skills for running a single live site, but he recommends the Jetpack route for multisite setups or any site where you don't want an agent to have full WP-CLI access.

#Who is affected

Anyone running a self-hosted WordPress site on Jetpack 15.8 or later, connected to WordPress.com, with a paid Jetpack AI or Jetpack Complete plan, who wants Codex or ChatGPT to edit posts, pages, design, or plugins. Sites on a paid WordPress.com plan use the same MCP server without Jetpack.

#What to do now

1. In WP Admin, open Jetpack, then Jetpack AI, then the MCP and Connectors tab, and turn on Enable MCP access.
2. Before connecting, choose which tool groups agents may read and which they may change, and leave anything you don't need switched off.
3. In Codex, run codex mcp add wpcom-mcp --url https://public-api.wordpress.com/wpcom/v2/mcp/v1. The OAuth sign-in starts on its own; if it doesn't, run codex mcp login wpcom-mcp.
4. Review the agent activity log in the same MCP and Connectors tab after each session.

If you manage one site and are comfortable giving an agent shell access, Coords says WP-CLI with the WordPress Agent Skills is still the stronger setup.

#What is not confirmed

Coords' preference for WP-CLI versus Jetpack is his own field opinion and is not independently verified. Plan requirements and tool group names come from Jetpack's and WordPress.com's docs as of Oct 13, 2026 and may change. DotsFeed did not test the connection itself.

Sources: Brian Coords on X, Jetpack: Connect an AI agent to your site with MCP, WordPress.com MCP server docs