Skip to content

TL;DR - WordPress MCP

  • Official WordPress MCP adapter bridging the Abilities API to AI agents, shipping in WordPress 6.9
  • Supports HTTP and stdio transport with permission checking tied to WordPress user roles
  • Works with Claude, Cursor, and VS Code, Plugin Directory tools included for developers
Pricing: Free forever
Best for: Individuals & startups

Pros & Cons

Pros

  • Official WordPress project, shipping in core with long-term maintenance guaranteed
  • User role-based permissions mean AI agents inherit existing WordPress access controls
  • Dual transport modes (HTTP + stdio) support both cloud-hosted and local development
  • Exposes the full plugin/theme ecosystem as AI-callable tools through the Abilities API

Cons

  • WordPress.com hosted version currently limited to read-only access
  • Self-hosted setup requires the MCP adapter plugin and OAuth configuration
  • Tool surface depends on which plugins expose abilities, coverage varies by installation

Key Features

Bridges the WordPress Abilities API to MCP, exposes plugins, themes, and core as AI-callable toolsHTTP and stdio transport modes for both remote server and local development useGranular permission checking tied to WordPress user roles (editor, admin, etc.)Plugin Directory MCP tools for readme validation, plugin status checks, and submissionsCompatible with Claude Desktop, Cursor, VS Code Copilot, and all MCP clientsShipping with WordPress 6.9 core, becoming the canonical MCP integrationOpen source with contributions from Automattic and the WordPress communityWordPress.com hosted integration for read-only site access (write access coming soon)

Pricing Plans

Open Source

Free

  • Full source code access
  • Community support
  • Self-hosted

What is WordPress MCP?

Editorial review
WordPress MCP is the official Model Context Protocol adapter for WordPress that bridges the Abilities API to MCP, enabling AI agents to discover and invoke WordPress plugin, theme, and core abilities programmatically. Maintained by Automattic and now part of the WordPress core project (shipping with WordPress 6.9), it lets AI tools like Claude Desktop, Cursor, and VS Code Copilot interact with WordPress sites through natural language. The adapter supports two transport modes: HTTP transport implementing the MCP 2025-06-18 specification for remote communication, and stdio transport for local development and CLI integration. WordPress abilities are exposed as MCP tools, executable functions that AI agents call to fetch data, update posts, run diagnostics, or manage site settings. Access controls follow WordPress user roles, so an editor-level connection cannot perform admin-only operations. WordPress.com's hosted MCP integration currently provides read-only access for surfacing site information and insights, with write access coming in a future update. For self-hosted WordPress, the MCP adapter plugin provides full read-write capabilities with granular permission checking. The Plugin Directory also offers a dedicated MCP server with tools for validating readme files, checking plugin review status, and submitting plugins. The adapter is open source on GitHub and is becoming the canonical plugin for MCP integration in the WordPress ecosystem.

Reviews

Be the first to review WordPress MCP

Your take helps the next buyer. Verified LinkedIn reviewers get a badge.

Write a review

Best WordPress MCP Alternatives

Top alternatives based on features, pricing, and user needs.

View full list →

Explore More

WordPress MCP FAQ

Is WordPress MCP official?

Yes. It is maintained by Automattic and is now part of WordPress core — shipping with WordPress 6.9. It bridges the WordPress Abilities API to MCP, so AI agents can discover and invoke plugin, theme, and core abilities.

What transport modes does it support?

Two modes: HTTP transport (MCP 2025-06-18 spec) for remote communication, and stdio transport for local development and CLI integration. Self-hosted WordPress gets full read-write capabilities via the adapter plugin.

Does it respect WordPress user roles?

Yes. Access controls follow WordPress user roles — an editor-level connection cannot perform admin-only operations. This ensures AI agents only do what the connected user is authorized to do.

Does WordPress.com support it?

WordPress.com's hosted MCP integration currently provides read-only access for surfacing site information and insights. Write access is coming in a future update. Self-hosted WordPress already supports full read-write via the plugin.

Is it free?

Yes. The MCP adapter is free and open source on GitHub. It works with any WordPress installation — self-hosted or WordPress.com. No additional licensing or subscription is required.

Source: github.com