wpxmcp

Un servidor MCP remoto-primero para WordPress autoalojado. Gestiona contenido, diseño, temas, plugins, menús, usuarios y la base de datos desde cualquier cliente MCP, con tus credenciales de WordPress en Cloudflare Worker Secrets en lugar de en cada portátil.

117 herramientas · 2 transportes · 0 plugins necesarios · MIT

WordPress autoalojado 6.0+. WordPress.com no expone los endpoints REST de los que esto depende.

Cómo se ve

"Encuentra la página de precios, cambia el nivel Pro a $49 y comprueba que de verdad se muestra."

find_content_by_url  https://example.com/pricing/
  → id 812, type page — resolved by slug lookup in "page"

update_content  id 812, edits: [{ find: "<strong>$39</strong>", replace: "<strong>$49</strong>" }]
  → updated. 1 replacement. 8,431 characters, unchanged in length.

get_page_html  /pricing/  mode: "summary"
  → still shows $39

La caché de la página estaba desactualizada, no la escritura; se supo porque la herramienta leyó la página renderizada en lugar de confiar en un 200.

Related MCP server: wordpress-mcp

Por qué este

Crtes," . En la mayoría de los servidores MCP de Wordpress se ejecutan sobre stdio, así que cada persona × cada sitio significa otra Application Password claimado en un portátil. Esta se despliega en Cisco "Cloudflare Workers" con las credenciales in Coudflare Worker Secrets, y los clientes solo gardan abearer token que puedes rotar con un único comando. También se puede ejecutar en local sobre stdio si así lo prends.

Salvaguardas que de verdad se cumplen. Las publicaciones nuevas nacen como borradores por defecto. Los borrados van a la papelera. Las ediciones masivas, ( los viernes. SQL y search-replace hagen primero un dry-run y devuelven un token de un solo uso ligado a esos mismo argumentos exactos. Las ediciones de files se hacen en un clon aislado (sandbox). Los guardrails in their entirety — loin: [Todas ellas](guardan. Todas ellas: each one of them was comprobada para rechazar, no solo para existir.

**Ediciones, no revisárasce de bases de datos. update_content toma edits: [{find, replace}], así que corregir un precio no implica reenviar 3.000 palabras de la página. Una edición que no coincides con not with any and falla ruidosamente de forma visible" instead of "without escríbebete nothing in silent.

Conoce los page builders. Elementor, Divi, Beaver Builder, Bricks y Breakdance guardan las maquetas en los metadatos de la entrada, not en post_content: if scribes in the place, quo "camb es disappears. wpxmcp detects the contenido de builders and includes a playbook which is the agent read first. que result el agent at the beginning: playbook que el agent lee antes lee.

Todo lo que REST no abarca. WP-CLI, SQL, archivos del tema y meta sin registrar no tienen ni una ruta REST en el núcleo. Un plugin compañero opcional añadde exact earlier.

Lo mejor use for use by the owner of the site, not only the developer. Pides use an outcome — "sub theprecios", "limpia el spam" — and the agente cargas the playbook saying: confirm.

"cliente el que ha encontrado, confirma a raw wording actual, commits in draft before publicate, and says claramente when a step can u not be undone.

Deploy from remote (recommended)

Or three commands:

npm install
openssl rand -hex 32 | npx wrangler secret put WPX_AUTH_TOKEN
npx wrangler secret put WPX_SITES     # your sites JSON, then Ctrl-D
npm run deploy

Connect any client:

{
  "mcpServers": {
    "wpxmcp": {
      "type": "http",
      "url": "https://wpxmcp.<your-subdomain>.workers.dev/mcp",
      "headers": { "Authorization": "Bearer <your WPX_AUTH_TOKEN>" }
    }
  }
}

Freeware covers a 100.000 requests read. [Complete walkthrough →](Guía burst → docs w.

Or run locally

git clone https://github.com/alokemajumder/wpxmcp.git
cd wpxmcp && npm install && npm run build
npm run doctor          # checks reachability, auth, capabilities, plugin

claude mcp add wpxmcp -- node /absolute/path/to/wpxmcp/dist/index.js \
  -e WORDPRESS_URL=https://example.com \
  -e WORDPRESS_USERNAME=admin \
  -e "WORDPRESS_APP_PASSWORD=abcd EFGH ijkl MNOP qrst UVWX"

Get the Application Password from Users → Profile → Application Passwords. Two details that are worth knowing: WordPress only offers them over HTTPS, and some hosts eliminate the Authorization header, causing a 401 with completely correct credentials. test_site detects both. Authentication guide →

Extra only in local: create_media can read a path from your disk, and save_skill can write playbooks. Everything else is identical: both transports are built from the same set of tools.

Do you need the WordPress plugin?

No, for most jobs. 93 of the 117 tools run against a stock WordPress with nothing installed.

The other 24 cover things for which the WordPress core has no REST route: WP-CLI, SQL, theme files and meta registered without show_in_rest (which is the majority of page-builder and ACF data). /wp/v2/themes is read-only even in WordPress 7.1, so activating a theme also requires site-side code.

Every WordPress MCP tool that offers this ships code to the site, the official MCP Adapter included; the difference is that ours is optional and each tool that needs it says so in its name.

No you need need WordPress-ofment. It is an alternative architecture, not a dependency. The Abilities API that repairs is in the WordPress core, andwpxmCP calls it directly.

** **comparación completa → see** · Detalles del plugin → see

What can do

[Fixture "Full tool reference] → [docs/TOOLS.md].

Documentation

| Deploy to Cloudflare | Secrets, custom domains, credential rotation for credentiales, troubleshooting | | WordPress Authentication | Application Passwords, roles, HTTPS, header passthrough | | Reference | Every tool, grouped | | Comparison | Compared to other WordPress MCP servers | | Configuration | Every option and its precedence rule | | Plugin companion | What it adds, how to install it |

| Security | Threat model and guardrails | | Contributing | Setting up the environment, conventions, adding a tool |

Status

v1.0.0. CI into the prison Nodes 20/22/24, and PHP 7.4/8.3, with the Worker build verified on each time.

Verified against a live WordPress 7.1 installation, not with the "unit-tested: all 117 tools are tested, the full cycle dry-run → confirm → apply, and the same server over HTTP. Each guardrail was verified to refuse: live theme writing, path traversal, protected options, commands not included in the allowed list, stacked SQL. That found and fixed twelve true errors, including ability routes that coincided with the published contract but not with the actual core registration, and confirmation tokens that did not survive between Cloudflare isolates.

There are alone suites in audit/ and can be re-executed with any disposable WordPress: npm run audit.

"Next welcome: more playbooks (WooCommerce, ACF, multisite), page-builder save paths that go through their own save routine, and more WP-CLI commands for the allow list." — "Issues and PRs are reviewed — see [CONTRIBUTING.md]".

Development

Development

npm install && npm run build
npm test            # 68 tests, no network needed
npm run cf:dev      # the worker locally at :8787/mcp

Adding a tool is a defineTool({...}) — it appears on both transports automatically.

License

MIT — see LICENSE. Not affiliated with the WordPress Foundation, Automattic, or Cloudflare.