To connect OpenClaw to WordPress, first install and onboard OpenClaw, then choose a connection based on where your site is hosted: WordPress.com’s official MCP service works for eligible WordPress.com and Jetpack-connected sites, while other self-hosted sites may use a separate MCP plugin. The connection details differ, and the available documentation does not provide a verified OpenClaw-specific setup command for either route.
1. Install and onboard OpenClaw
OpenClaw must be running before you can connect a WordPress service. Follow the current OpenClaw documentation for the installer appropriate to your operating system. The installer starts onboarding; complete openclaw onboard and configure an API key for your chosen model provider. The current documentation recommends Node 26 and lists Node 24.16+ or 26.1+ as supported.
As an Amazon Associate I earn from qualifying purchases.
If the initial Gateway is running in the foreground, stop it with Ctrl+C before installing the background service. Then run openclaw gateway install and open the dashboard with openclaw dashboard.
2. Choose the WordPress connection that fits your site
| Route | Who it serves | Authentication and controls | OpenClaw setup detail |
|---|---|---|---|
| WordPress.com MCP | WordPress.com sites on paid plans; free sites during their first 30 days; self-hosted WordPress connected through Jetpack with a Jetpack AI or Jetpack Complete plan | Browser-based OAuth 2.1; access can be revoked under Connected Apps | The endpoint is documented, but an exact current OpenClaw configuration entry or UI sequence is not |
| WSP MCP plugin | Ordinary self-hosted WordPress, according to the plugin listing | The listing describes a private connection key or application password, WordPress-user permissions, an audit log, and write tools disabled until enabled | The listing claims OpenClaw support, but does not provide a written OpenClaw configuration snippet in the reviewed text |
WordPress.com or a Jetpack-connected site
WordPress.com’s official MCP endpoint is https://public-api.wordpress.com/wpcom/v2/mcp/v1. To use it, enable MCP in your WordPress.com account settings, add the endpoint through an MCP-capable client, then complete authorization in the browser. WordPress.com documents OAuth 2.1, including PKCE, dynamic client registration, token rotation, and revocation; it says this flow avoids storing WordPress credentials on your computer or sharing them with the AI client. These details describe WordPress.com’s service, not the separate plugin route.
#1 Best Overall
WordPress.com documents commands for other clients, including Codex, but those commands are not OpenClaw commands. Do not paste them into a shell expecting them to configure OpenClaw. Use the MCP or plugin interface available in your installed OpenClaw version, and confirm its current instructions before proceeding.
Other self-hosted WordPress sites
The WSP MCP WordPress.org listing says the plugin supports OpenClaw. Its described flow is to install and activate the plugin, choose enabled tools in its MCP settings, copy the displayed connection configuration into the AI client, and restart that client. Because the listing does not include a written OpenClaw-specific configuration snippet in the reviewed text, verify the current plugin instructions and compatibility before relying on this route. Its descriptions of credentials, logging, and controls are the publisher’s claims, not an independent security audit.
Plugin-directory submissions are a different use
The official WordPress.org MCP service supports plugin-directory tasks such as validating a plugin readme, retrieving review status, and submitting a plugin. It is not a general connection for editing posts or managing an ordinary WordPress site.
PC 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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match3. Authorize the connection and verify the site
- Enable the chosen route. For WordPress.com, turn on MCP in account settings. For the self-hosted plugin route, install and activate the plugin, then enable only the tools you intend to use.
- Add the server in OpenClaw. Use the MCP or plugin connection interface present in your installed version. Enter the WordPress.com endpoint above if that is your route, or use the connection configuration displayed by the self-hosted plugin. The available documentation does not establish a universal OpenClaw command or configuration format for these steps.
- Complete authorization. For WordPress.com, finish the browser OAuth flow. For a plugin route, follow its current connection instructions and use an account with only the permissions the intended tasks require.
- Start with a read-only check. Ask OpenClaw for a low-risk piece of information, such as the site name or a known post, and confirm the response belongs to the intended site. Review enabled tools before asking the agent to make changes.
- Test writes cautiously. If you enable write tools, begin with a low-impact change you can inspect and undo. Check the resulting content in WordPress rather than assuming that a successful agent response proves the intended change was made.
The read-first smoke test is a practical precaution, not an official OpenClaw-specific validation checklist.
How do I set up WordPress MCP for development?
For a WordPress.com site, enable MCP in account settings, connect an MCP-capable client to https://public-api.wordpress.com/wpcom/v2/mcp/v1, and approve access in the browser. WordPress.com says all paid plans include MCP access and free sites have access during their first 30 days. For a self-hosted site connected through Jetpack, the documented requirement is a Jetpack AI or Jetpack Complete plan. The endpoint and OAuth process are documented by WordPress.com; the exact current OpenClaw configuration steps are not.
How do I connect WordPress with OpenClaw?
For eligible WordPress.com or Jetpack-connected sites, use the official WordPress.com MCP endpoint and OAuth flow. For other self-hosted sites, the WSP MCP listing claims OpenClaw support and describes copying its displayed configuration into an AI client. In either case, follow the current instructions in your installed OpenClaw version and the relevant service; do not assume that commands documented for another client apply to OpenClaw.
Quick Recap
Review access and protect site changes
- WordPress.com: The documented OAuth flow uses browser authorization. WordPress.com says you can disconnect access under Security → Connected Apps.
- Self-hosted plugin: The WSP MCP listing describes a private connection key or application password, permissions tied to a WordPress user, an audit log, and write tools disabled initially. Confirm those controls in the current plugin settings before connecting or enabling writes.
- Limit the tool set: Enable only the actions needed for your workflow, especially when an agent can publish, edit, or delete content.
- Keep custom development separate: OpenClaw’s Plugin SDK overview labels plugin APIs experimental. A remote MCP connection does not by itself require writing a custom OpenClaw plugin.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
