What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
WordPress MCP integration connects an AI client to WordPress services or site capabilities through the Model Context Protocol (MCP). It is not one universal setup: the right route depends on whether you want to work with a WordPress.com account, expose a self-hosted site’s functionality, or use AI tools for WordPress.org plugin development.
What WordPress MCP integration means
MCP lets compatible AI clients communicate with services that provide tools and other capabilities. In WordPress, “MCP integration” can refer to three distinct routes. They serve different goals and should not be treated as interchangeable.
| Route | Best suited to | How it works |
|---|---|---|
| WordPress.com MCP server | Working with sites associated with an eligible WordPress.com account | A hosted MCP server connects an enabled account to compatible clients. Qualifying self-hosted sites connected through Jetpack can use the same server and tool catalog. |
| WordPress MCP Adapter | Making selected capabilities available from a self-hosted WordPress site | The official adapter bridges the WordPress Abilities API and MCP. Registered abilities can be exposed as tools, resources, or prompts. |
| WordPress.org Plugin Directory MCP server | WordPress plugin authors using AI during development and submission | A separate service helps AI tools consult plugin guidelines, validate readmes, check submission status, and work with submissions. It is not a general connection to a live site. |
For hosted account access, WordPress.com documents the endpoint https://public-api.wordpress.com/wpcom/v2/mcp/v1 in its MCP guide. The Adapter and Plugin Directory service are separate projects with different setup instructions.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Which WordPress MCP route should you use?
Choose WordPress.com MCP for account and site operations
Use the hosted route if your goal is to connect an eligible WordPress.com account to an MCP-enabled client. It can also cover qualifying self-hosted sites linked through Jetpack. The account owner can choose read-only or full access, and account-level tool settings are shared by connected clients.
#1 Best Overall
Choose the MCP Adapter to expose a self-hosted site’s abilities
Use the official WordPress MCP Adapter when you are developing an integration for a self-hosted site and want to decide which registered WordPress abilities an MCP client can access. Its capabilities depend on what the site registers and authorizes; installing the adapter alone does not mean every site function is available.
Choose the Plugin Directory server for plugin work
Use the WordPress.org Plugin Directory MCP service for plugin-author tasks such as checking directory guidance or validating a readme. It is not the method for giving an AI client access to a site’s posts, settings, or custom functionality.
WordPress.com MCP: eligibility and connection
Check access for your site type
WordPress.com’s plan documentation, as reported on October 7, 2026, says MCP is available on all paid plans. A free site can access MCP during its first 30 days after creation. A qualifying self-hosted site connected through Jetpack requires Jetpack AI or Jetpack Complete. Plan rules may change, so confirm current eligibility in the WordPress.com MCP support documentation before configuring a client.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsConnect an MCP-enabled client
- Enable MCP: In your WordPress.com account settings, turn on MCP access. Review the available access setting and select read-only or full access according to the tasks you intend to allow.
- Add the server to your client: Use the documented endpoint,
https://public-api.wordpress.com/wpcom/v2/mcp/v1, in the client’s MCP server configuration. The exact configuration format depends on the client. - Authorize the connection: For browser-based clients, WordPress.com describes OAuth 2.1 authorization through the browser. The hosted connection requires no additional software installation, according to its developer guide.
- For a custom client, follow the documented flow: WordPress.com’s guidance specifies dynamic client registration and PKCE, followed by requests to the endpoint using a bearer token. Follow the current developer documentation for the client’s implementation details.
Self-hosted WordPress MCP Adapter: development setup
The Adapter is a developer integration, not the same hosted connection as WordPress.com MCP. It maps registered WordPress Abilities to MCP-facing tools, resources, or prompts. A developer can use its default server or configure a custom one, with transport chosen for the environment.
Local development with STDIO
The official developer example uses WP-CLI and the STDIO transport for local development. In this setup, the MCP client communicates with the local server process through standard input and output. Use the installation and client-configuration steps in the Adapter documentation; the client’s configuration syntax is client-specific.
Publicly accessible sites or HTTP transport
For a publicly accessible site or a non-STDIO setup, the Adapter documentation describes an HTTP route using Automattic’s remote proxy, with WordPress application-password or custom OAuth authentication. Follow the Adapter’s current guidance for the selected authentication method and transport rather than assuming that the local STDIO configuration applies to a remote site.
Quick Recap
Permissions and security: decide what the client may do
- Limit WordPress.com access: Choose read-only access when the workflow only needs to retrieve information. Full access is broader and may permit write actions; enable it only when those actions are necessary.
- Review shared account settings: WordPress.com account-level tool settings apply across connected clients, so consider the effect on every client using that account.
- Expose only intended abilities: With the Adapter, developers control which registered abilities are available. Select abilities deliberately and enforce authorization for them.
- Review generated actions: Check what the client proposes to do before allowing changes, and grant only the access required for the workflow.
Common confusion about WordPress MCP
- “Does the Plugin Directory MCP server connect to my website?” No. It supports plugin development and directory-related tasks; use WordPress.com MCP or the MCP Adapter for site capabilities, depending on the site and goal.
- “Does the Adapter automatically expose every WordPress feature?” No. MCP-facing capabilities depend on the abilities registered and exposed by the site, along with their authorization rules.
- “Is there one setup that works for every client?” No. Authentication, transport, and configuration vary by route and client. WordPress.com documents browser OAuth for its hosted service, while Adapter development may use local STDIO or an HTTP setup.
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.
