Free tools Windows power users keep installed
One-click scans. No signup required.
The right way to connect an AI agent to WordPress depends on where your site is hosted and what you want the agent to do. WordPress.com and Jetpack-connected sites can start with WordPress.com’s managed MCP service; self-hosted sites needing custom functions can use the official WordPress MCP Adapter with registered Abilities API functions. WordPress.org’s MCP server is for plugin-directory work, while WP Engine’s documented service is still in closed beta. Plugin-based MCP servers and direct REST API calls are other options, but require careful review of permissions and data handling.
Which WordPress MCP option fits your site?
| Your situation | Starting point | Trade-off to check |
|---|---|---|
| WordPress.com or Jetpack-connected self-hosted site | WordPress.com MCP server | Plan eligibility, account-level tool settings, and user-role limits |
| Self-hosted site needing custom site operations | Official WordPress MCP Adapter plus registered abilities | Work to implement and safely scope the abilities |
| Plugin author preparing or submitting to WordPress.org | WordPress.org MCP server | Narrow purpose, compatible client, and Node.js prerequisite |
| WP Engine customer with beta access | WP Engine AI MCP service | Closed-beta access and possible changes |
| Narrow workflow or no suitable hosted service | Third-party MCP plugin or direct REST API | Plugin trust and upkeep, or the client’s API and authentication design |
Compare any option by the hosting plan it requires, the precise operations it exposes, its authentication and transport, permission controls, and how mature and maintained it is. “MCP support” alone does not tell you whether an agent can safely perform the task you have in mind.
As an Amazon Associate I earn from qualifying purchases.
WordPress.com’s managed MCP server
WordPress.com hosts an MCP endpoint at https://public-api.wordpress.com/wpcom/v2/mcp/v1. It can connect to sites in the account; self-hosted WordPress sites connected through Jetpack use this same service rather than a separate Jetpack MCP endpoint. WordPress.com’s developer documentation says access is available on all paid WordPress.com plans, while a free WordPress.com site has access for its first 30 days. Self-hosted Jetpack sites require a Jetpack AI or Jetpack Complete plan. Plan eligibility can change, so confirm it in the current documentation before setting up access.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Connection uses OAuth 2.1 with a browser authorization flow. WordPress.com documents procedures for Claude, VS Code, Cursor, ChatGPT, and Codex; other MCP-compatible clients may also connect. Account tool access can be enabled and tool groups customized. Take particular care with write access: WordPress.com Support says Read and Write groups are enabled by default when MCP is turned on. Site roles still limit what a user can do; as the support page puts it, “MCP respects the user role permissions on your site.” See WordPress.com’s MCP support documentation for role and tool details.
#1 Best Overall
When this is a good fit
- You already use WordPress.com or have connected a self-hosted site through Jetpack.
- You want a managed endpoint rather than operating a separate server or proxy.
- The site’s plan, user role, client, and account-level tool policy meet your needs.
Official MCP Adapter and the Abilities API
The official WordPress MCP Adapter maps registered Abilities API functions into MCP tools an agent can discover and call. The adapter supplies a protocol and transport layer; it does not automatically provide a complete set of useful site actions. What an agent can do depends on abilities registered by WordPress core, installed plugins, or custom code implemented for the site. The MCP Adapter plugin page describes HTTP and STDIO transports and notes that sites need registered abilities.
The Developer Blog describes a local WP-CLI/STDIO setup and an HTTP approach for publicly accessible sites using Automattic’s @automattic/mcp-wordpress-remote proxy. Its example uses application passwords or custom OAuth for authentication. These implementation details can change with adapter and client versions, so follow the current setup instructions. If several plugins rely on the adapter or Abilities API, the post points to Jetpack Autoloader as a way to avoid version conflicts.
When this is a good fit
- You run self-hosted WordPress and need site-specific operations rather than a general-purpose hosted connection.
- You can identify or implement the abilities the agent actually needs.
- You can control transport, authentication, user permissions, and which abilities are exposed.
Before connecting a client, inventory the registered abilities and distinguish read, write, and delete operations. Use an account with only the capabilities needed for the workflow; do not use a broad administrator credential simply to make setup easier.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →WordPress.org’s MCP server is for plugin-directory work
WordPress.org documents an MCP server for preparing, validating, and submitting plugins to the WordPress Plugin Directory. Its workflow can expose plugin guidelines, readme validation, and submission status. It is not the general-purpose way to manage posts or settings on an arbitrary WordPress site. The Plugin Handbook documentation lists an account, an MCP-compatible client, and Node.js version 18 or later among the prerequisites.
Rank #3
When this is a good fit
- You are a plugin author working with the WordPress.org directory.
- Your task is directory preparation or submission, not managing a separate WordPress installation.
WP Engine’s AI MCP service is a closed beta
WP Engine documents an AI MCP service that can list account sites, search and run abilities, and create, update, or delete posts and pages. Its documentation labels the service “Closed beta” and warns that endpoints, tools, and authentication may change before general availability. It is therefore an option only for WP Engine customers who can access the beta, not a generally available connector. Check WP Engine’s current documentation for eligibility, supported operations, client requirements, and authentication.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Third-party MCP plugins and direct REST API calls
WordPress.org’s Plugin Directory includes third-party MCP options. For example, the publisher of Easy MCP AI says its plugin runs an MCP server inside WordPress, supports various MCP clients, and offers an Abilities API adapter. Those are publisher claims, not an independent security, compatibility, performance, or feature assessment.
Rank #4
A tool-calling agent can also use the WordPress REST API directly for a small, defined workflow. The Agent Toolbelt listing describes exposing selected abilities through the official adapter and providing direct agent instructions; that is product documentation, not an independent audit. Direct API access may be simpler or more complex depending on the client, operations, and authentication design.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Best Value
What to check before choosing a plugin or API route
- Which WordPress, PHP, and plugin versions are supported, and whether the plugin is maintained.
- Where requests are processed and whether a separate vendor-operated proxy is involved.
- What user capabilities and individual tools are exposed, including write and delete actions.
- How credentials are stored, requests are authenticated, and activity can be audited.
- Whether the agent’s workflow is narrow enough for direct API calls, or needs MCP discovery and reusable tools.
A practical selection checklist
- Identify the hosting model. Confirm whether the site is on WordPress.com, self-hosted with Jetpack, another self-hosted host, or WP Engine.
- Write down the required operations. Separate reading from creating, updating, and deleting content; include commerce or plugin-specific actions only if the workflow needs them.
- Match the operation to a capability. For the official adapter, verify that a registered ability exists or can be implemented. For a hosted service or plugin, verify that its actual tools cover the job.
- Review access before authorizing. Check the connecting user’s WordPress role, per-tool settings, authentication flow, and any external proxy. Disable unneeded write or delete tools.
- Check maturity and prerequisites. Confirm plan access, client support, required software, plugin maintenance, and beta status in the provider’s current documentation.
- Test with a low-risk task. Start with a read operation or a draft rather than a live destructive action, then verify the result in WordPress.
What to remember about WordPress MCP alternatives
- The official MCP Adapter exposes registered abilities; it is not itself a ready-made catalog of every site function.
- WordPress.com’s managed service also serves Jetpack-connected self-hosted sites, subject to plan requirements.
- Enabling a connection can include write tools by default on WordPress.com, so inspect account settings and the connecting user’s role.
- WordPress.org’s server targets plugin-directory workflows, while WP Engine’s documented option is closed beta.
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.
