Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11For most WordPress plugins, start with the MCP Adapter’s default server. Register a custom server through the Adapter when your plugin needs its own MCP identity, route, transport configuration, or handlers. Build an independent MCP server only when the Adapter’s WordPress integration does not fit or the server must run outside WordPress—and you are prepared to own the integration, permissions, protocol behavior, deployment, and maintenance.
What “Adapter vs. custom server” actually means
The WordPress MCP Adapter is itself an MCP implementation: it connects WordPress’s Abilities API to the Model Context Protocol. The practical choice is usually among three approaches—not between using MCP and not using it:
- Default Adapter server: expose opted-in WordPress Abilities through the shared default server.
- Custom server through the Adapter: use the Adapter package but register a server with plugin-specific configuration or handlers.
- Independent custom server: build a separate MCP implementation and its connection to WordPress. This is an architectural option, not the approach demonstrated by the cited WordPress developer materials.
WordPress describes the default server as sufficient for most requirements. The Adapter can expose Abilities as MCP tools, resources, or prompts. Its default server uses three meta-tools to discover available Abilities, retrieve information about an Ability, and execute one.
How the options compare
| Decision area | Default Adapter server | Custom server through Adapter | Independent custom server |
|---|---|---|---|
| WordPress connection | Uses the WordPress Abilities API and the default server’s meta-tools. | Uses the Adapter package while allowing server-specific configuration. | You design and maintain the bridge to WordPress functionality. |
| Interface and identity | Shared default server and common Ability discovery, information, and execution flow. | Can have a distinct server identity, route, description, version, transport configuration, and server-specific handlers. | Designed and implemented separately to meet requirements outside the Adapter model. |
| Exposure and permissions | Choose which Abilities are exposed; authenticated identity and WordPress permission checks still govern execution. | Shape the server boundary and listed Abilities, while reviewing the same Ability-level permissions. | You must design and enforce the exposure, identity, and authorization model. |
| Setup and ownership | Install the Adapter and connect a client to the default endpoint using an appropriate transport. | Include the package, initialize it, register the server, and manage dependency/version compatibility. | Implement and operate the server, WordPress integration, protocol behavior, deployment, and ongoing maintenance. |
| Typical fit | Common cases where WordPress Abilities express the functions a client needs. | A plugin needs a tailored MCP interface but still benefits from the Adapter’s WordPress integration. | Requirements that do not fit the Adapter integration model or require the server to operate outside WordPress. This is an architectural inference, not a comparative result established by WordPress documentation. |
The WordPress materials describe the first two approaches directly. The independent-server column is a design comparison: the cited materials do not offer a measured, like-for-like evaluation of independent implementations against the Adapter.
#1 Best Overall
When to use the default server
Choose the default server when your plugin’s functionality maps cleanly to WordPress Abilities and its shared discovery-and-execution interface is adequate. It avoids creating another server boundary for a client to connect to and for your team to configure.
- The client can discover and invoke the Abilities you intentionally expose.
- The default server’s common meta-tools are enough; you do not need a separate server identity or custom handlers.
- You can make exposure decisions through Ability metadata and use WordPress capability checks to govern execution.
Abilities are private by default. Exposing an Ability to MCP is a deliberate choice, not an automatic consequence of installing the Adapter.
When to register a custom server through the Adapter
Register a custom server when a plugin needs its own MCP-facing boundary but should continue to use the Adapter’s WordPress integration. This is the middle option: more control over the server interface than the default provides, without independently rebuilding the WordPress bridge.
The documented registration pattern uses the mcp_adapter_init action and create_server(). The server configuration includes an identifier, REST namespace and route, name, description, version, and transport list. The plugin can also provide server-specific handlers. The exact configuration should follow the current Adapter package documentation for the version in use.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →For plugin development, the Adapter can be included as a Composer package. Where multiple plugins may depend on the Adapter or Abilities API, WordPress advises considering Jetpack Autoloader to help avoid dependency-version conflicts.
When an independent MCP server may be justified
A separate implementation may make sense if the required interface or runtime falls outside the Adapter’s integration model—for example, if the server must run outside the WordPress process. That is a reasoned architectural choice, not a WordPress-documented guarantee that a separate server is faster, safer, cheaper, or easier.
Rank #4
With an independent implementation, the project takes responsibility for the full connection between the MCP client and WordPress: identity mapping, authorization, Ability or other WordPress functionality integration, protocol behavior, deployment, and maintenance. Before choosing this route, validate those responsibilities against current MCP and WordPress documentation. If the need is only a different route or server identity, first assess whether registering a custom server through the Adapter meets it.
Connecting a local or remote WordPress site
The documented local workflow serves the Adapter through WP-CLI over STDIO; the remote workflow uses HTTP. The default REST endpoint is /wp-json/mcp/mcp-adapter-default-server. A custom server can define its own route. Client configuration differs, so use the instructions for the specific MCP client rather than assuming one configuration works everywhere.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Confirm the installation channel and requirements. A Learn WordPress lesson lists WordPress 6.9 or later and PHP 7.4 or later for the plugin, and describes installing from the project’s GitHub Releases. It also says the plugin is not yet listed on WordPress.org. These are time-sensitive details; check the current release and repository before installing.
- Choose the server boundary. Use the default endpoint for the shared server, or register a custom server if the plugin needs its own route or configuration.
- Select the transport for the deployment. Use the documented WP-CLI/STDIO workflow for local development or HTTP for remote access.
- Configure the MCP client. Point it at the appropriate server and follow that client’s current setup instructions. Do not assume the local STDIO setup and a remote HTTP connection use identical configuration.
- Test discovery and execution separately. Confirm that intended Abilities are discoverable and that execution succeeds only for an authenticated user with the required permissions.
Can an MCP server access WordPress securely?
It can be configured to expose selected WordPress functionality, but the security boundary depends on both what is exposed and which authenticated user invokes it. Public discovery is not the same as unrestricted execution: the authenticated user’s capabilities and an Ability’s permission callback remain relevant.
- Review each exposed Ability. Check its metadata, callback behavior, and any data it returns or changes.
- Use a least-privilege account. Grant the client only the capabilities needed for the intended tasks. A documented local example uses a WordPress user argument and illustrates an admin user; that example is not a reason to give an AI client administrator access.
- Review the default server’s capability checks. The checks for discovering Abilities, retrieving Ability information, and executing Abilities are configurable.
- Test the actual deployment. Check both what unauthenticated or lower-privilege users can discover and what they can execute, including the Ability’s permission callback.
Mind the WordPress version when reasoning about REST visibility. The official Ability guide says core begins applying meta.public to REST API visibility in WordPress 7.1. On WordPress 6.9 and 7.0, the Adapter honors meta.public for MCP exposure, but REST API access still requires meta.show_in_rest to be true. MCP exposure and REST API visibility are distinct surfaces.
Is WordPress.com’s managed MCP service another option?
Yes. WordPress.com documents a hosted MCP endpoint at https://public-api.wordpress.com/wpcom/v2/mcp/v1. One connection can reach sites on the account, and authentication uses OAuth 2.1 through browser authorization. This is a managed account route, separate from installing the WordPress MCP Adapter or registering a custom server through it.
According to WordPress.com’s documentation accessed in 2026, MCP is available on paid WordPress.com plans. A free WordPress.com site can use it during the first 30 days after site creation. Self-hosted sites connected through Jetpack require Jetpack AI or Jetpack Complete. Verify current plan terms and eligibility before relying on this option.
Recommended Free Tools
Quick Recap
Make the choice by the boundary you need
- Use the default Adapter server when opted-in WordPress Abilities and the shared discovery and execution flow are sufficient.
- Register an Adapter custom server when you need a plugin-specific server identity, route, transport configuration, or handlers while keeping the Adapter’s WordPress integration.
- Build independently only when requirements exceed that integration model or the server must live outside WordPress, and account for the additional security and operational ownership.
- Use WordPress.com’s hosted route if its account-based access, OAuth flow, and current plan eligibility fit better than operating a site-specific server.
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.
