How to connect OpenClaw to WordPress

Link your WordPress site once in Ryze AI, save one MCP URL in your OpenClaw Gateway, sign in, then ask your agent to read, create and edit posts, pages and media.

Your MCP URL
https://connector.get-ryze.ai/mcp

Save it in OpenClaw as a streamable-http server named ryze. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026

Quick answer

The main way to connect OpenClaw to WordPress is the Ryze AI connector. Link the site in Ryze AI first, with an application password for a self-hosted install or a WordPress.com sign-in for WordPress.com and Jetpack sites. Then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using the CLI, Settings > MCP in the Control UI or openclaw.json. After one sign-in OpenClaw can list 9 WordPress tools: two that read, six that write and one that deletes.

  1. On a self-hosted site, create an application password under Users > Profile in wp-admin
  2. In Ryze AI open Integrations, click Connect on the WordPress card and link the site
  3. Save the Ryze AI server in OpenClaw with openclaw mcp set, the Control UI or openclaw.json
  4. Run openclaw mcp login ryze, click Allow connection, then ask about your posts and pages

OpenClaw to WordPress at a glance

FactDetail
Main way to connectThe Ryze AI connector, saved in OpenClaw as one remote MCP server named ryze
Server addresshttps://connector.get-ryze.ai/mcp, with transport set to streamable-http
OpenClaw sign-inOAuth to Ryze AI with openclaw mcp login ryze, or Sign in under Settings > MCP for an administrator. A Ryze AI API key in a bearer header is the other route
How the site is linkedSelf-hosted: Site URL, wp-admin username and an application password. WordPress.com or Jetpack: a sign-in on WordPress.com
WordPress tools9: two read, six write and one delete
Can it change the siteYes, through the write, edit and delete tools, within what the linked WordPress user may do. OpenClaw's docs describe no per-call prompt for its built-in runtime, so limit the tools yourself (see the approvals note below)
Self-hosted onlyPlugin installs, the Yoast SEO and Rank Math bridges and head code, all with an administrator's application password
OpenClaw plan neededNone to buy. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier
Ryze AI priceSEO Starter is $129 per month with a 3-day free trial. Adding the connector is free; the tools need an active plan or trial
WordPress's own option for OpenClawNo WordPress page opened names OpenClaw for its own servers. The AI Engine plugin names OpenClaw on its page. See the ways table
Last testedConnector sign-in check on November 13, 2026. Nine WordPress reads on November 14, 2026, over a WordPress.com connection. No step inside OpenClaw was run

Before you start

  • OpenClaw. It is an open-source project under the MIT license that you host yourself. You need a running Gateway and one of three things: the openclaw command on the Gateway machine, administrator access to the Control UI, or write access to the Gateway's openclaw.json.
  • WordPress access. Self-hosted: a user who can create an application password, on a site served over HTTPS (WordPress offers the feature by default only there, and an administrator can switch it off). WordPress.com or Jetpack: a WordPress.com account that reaches the site, plus the Jetpack JSON API module on Jetpack sites. Plugin installs, the SEO bridges and head code need an administrator.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial. Adding the connector is free, but the WordPress tools need any active Ryze AI plan or trial.
  • A note on testing. Ryze AI has no help-center page for OpenClaw and the OpenClaw steps were not run for this page. They follow OpenClaw's own documentation for remote servers that use OAuth, as read on November 15, 2026.

How to connect OpenClaw to WordPress

The first two steps happen in WordPress and Ryze AI, the next three in OpenClaw, and the last is your first prompt. The connector URL is the same for every user.

  1. Create an application password in WordPress

    For a self-hosted site, sign in to wp-admin, open Users > Profile and scroll to Application Passwords. Type a name such as Ryze AI, click Add New Application Password and copy the result, because WordPress shows it once. A WordPress.com or Jetpack site skips this step.

  2. Link the site in Ryze AI

    Sign in to Ryze AI, open Integrations and click Connect on the WordPress card. On the Self-hosted site tab enter the Site URL, the username you use at wp-admin and the application password, then click Continue. On the WordPress.com / Jetpack tab, sign in on WordPress.com, approve access and choose the site. Afterwards, View on the card lets you set the Author and Category for new posts.

  3. Save the Ryze AI server in OpenClaw

    Stop the Gateway with openclaw gateway stop, because OpenClaw 2026.10.10 (November 3, 2026) holds back CLI changes to MCP settings while a Gateway runs. Then run: openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'. The same entry can go under mcp.servers in ~/.openclaw/openclaw.json, or be added with Add server under Settings > MCP in the Control UI while the Gateway runs.

    openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryze
  4. Sign in to Ryze AI from OpenClaw

    Run: openclaw mcp login ryze. A browser opens on the Ryze AI page. Sign in if asked, choose the workspace that holds WordPress and click Allow connection, then start the Gateway again. An administrator can instead click Sign in for the ryze server under Settings > MCP.

  5. Finish the sign-in on another machine if needed

    If the browser is not on the machine that runs OpenClaw, approve the sign-in there and hand the code it returns to openclaw mcp login with the --code option.

  6. Ask your first question

    Once credentials exist, OpenClaw adds the server to the agent runtime. If you saved the connector before the site was linked in Ryze AI, remove the entry and save it again so the tool list refreshes. Then ask: List my 10 most recent WordPress posts with title, status and publish date.

The Ryze AI help center page for WordPress covers the WordPress side of the connection. OpenClaw does not have its own Ryze AI help page; the Ryze AI developers page covers the MCP URL for other clients.

Sources: OpenClaw MCP documentation, OpenClaw MCP transports, application passwords guide, Ryze AI WordPress guide. OpenClaw pages checked November 15, 2026, WordPress pages November 14, 2026.

CLI, Control UI, openclaw.json and API key

OpenClaw CLI

set writes the server definition and login runs the OAuth flow; the credentials stay on the Gateway host. Start the Gateway again afterwards. To see what is saved, openclaw mcp show ryze, list and status print it, and they keep working while the Gateway runs.

openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryze

Control UI: Settings > MCP

Open the MCP page of the Control UI (/settings/mcp, with /mcp as an alias), choose Add server under Configured servers, name it ryze, pick Streamable HTTP and paste the URL. OpenClaw's docs put the OAuth settings in the scoped config editor on that page, so set auth: "oauth" there and click Sign in. Adding a server needs administrator access. Inside a chat, + > Plugins > Add MCP server saves a server too.

openclaw.json

Edit ~/.openclaw/openclaw.json, which is JSON5, so comments and trailing commas are allowed. The Gateway watches the file and applies the change. Then sign in with openclaw mcp login ryze on a stopped Gateway, or use Sign in under Settings > MCP.

{ mcp: { servers: { ryze: { url: "https://connector.get-ryze.ai/mcp", transport: "streamable-http", auth: "oauth", }, }, }, }

A Ryze AI API key instead of OAuth

If you want a Ryze AI API key in place of the browser sign-in, leave out auth: "oauth" and send the key as a bearer header. OpenClaw ignores static Authorization headers while auth: "oauth" is on. Keep the key in an environment variable: a ${RYZE_API_KEY} reference does not trigger the literal-value warning of openclaw doctor when the variable is set. This key belongs to Ryze AI and is a different secret from the WordPress application password.

ryze: { url: "https://connector.get-ryze.ai/mcp", transport: "streamable-http", headers: { Authorization: "Bearer ${RYZE_API_KEY}" }, }

A remote entry takes the transport streamable-http or sse, and OpenClaw reads an entry with no transport as sse, so set streamable-http for this address. A request times out after 60 seconds by default, and listing the tools at session start gets 10 seconds when requestTimeoutMs is not set.

OpenClaw and MCP: the facts in one table

TopicWhat OpenClaw's documentation says
Where a server is addedSettings > MCP > Add server in the Control UI, + > Plugins > Add MCP server in a chat, openclaw mcp add or set in a terminal, or mcp.servers in ~/.openclaw/openclaw.json
Config file~/.openclaw/openclaw.json in JSON5, applied by the Gateway when the file changes
Transportsstdio for local commands, plus SSE and Streamable HTTP for addresses
Sign-inauth: "oauth" on an HTTP entry, then openclaw mcp login with the Gateway stopped, or Sign in under Settings > MCP for an administrator
Whose accountOne shared credential that the operator manages by default. Per-requester sign-in needs oauth.identity set to per-requester and gateway.publicOrigin set to an HTTPS origin
ApprovalMCP tools follow OpenClaw's tool profiles and tool policy. Per-call prompts are documented for Codex runs only
Tool namesThe agent sees <server>__<tool>, so a tool such as wordpress__read can carry the server name as a prefix. Run openclaw mcp doctor ryze --probe to see the exact names
PlanNo paid tier; MIT licensed and self-hosted
Admin controlsAdding a server from a chat and signing in from Settings need administrator access. enabled: false keeps an entry and hides its tools

Sources: OpenClaw MCP documentation, OpenClaw config extensions, OpenClaw MCP registry commands. Checked November 15, 2026.

Other clients

The same URL works in other MCP clients. The site is linked once in Ryze AI, so nothing changes in WordPress.

Claude Code

Claude Code registers the same URL with one claude mcp add command. How to connect Claude Code to WordPress.

Codex

Codex takes the connector URL through its own MCP settings. How to connect Codex to WordPress.

Claude and ChatGPT

Both add https://connector.get-ryze.ai/mcp as a custom connector. In ChatGPT it is an app under Settings > Apps. If the connector was added before the site was linked in Ryze AI, remove and re-add it so the tool list refreshes.

WordPress access, credentials and roles

WordPress never talks to OpenClaw directly. Ryze AI holds the WordPress credential and OpenClaw signs in to Ryze AI. Four things decide what your agent can reach on the site.

The WordPress user behind the credential
An application password acts as the user who made it. If that user cannot delete posts in wp-admin, the agent cannot delete them either. Plugin installs, the SEO bridges and head code need an administrator.
Self-hosted or WordPress.com
A self-hosted connection reaches every REST route the site exposes. A WordPress.com connection reaches only the core /wp/v2 routes, with no plugin installs, SEO bridges or head code.
One shared sign-in
By default OpenClaw's OAuth credential is shared and operator-managed, so everyone who talks to that agent edits the site through the one Ryze AI sign-in behind it. Per-requester sign-in needs gateway.publicOrigin set to an HTTPS origin.
What stands in front of a change
No prompt is documented for each call in OpenClaw's built-in runtime. The controls are your tool policy and a toolFilter, described under the tools table below.

What each job needs from the WordPress user

WordPress has no scope list for application passwords. A password acts as its user, so the table shows what each job needs from that user and from the site.

JobWhat the WordPress user needs
Read posts, pages, media, categories and tagsA user who can view them. Works on self-hosted and WordPress.com connections
List installed pluginsA user with the activate_plugins capability, which administrators hold
Create or update a post or pageA user who may publish or edit that content in wp-admin
Delete a postA user with delete permission in wp-admin
Install a plugin or add head codeAn administrator on a self-hosted site
Write Yoast or Rank Math fieldsAn administrator, a self-hosted site and the one-time bridge

The two credential types

Ryze AI takes two kinds of WordPress credential, and each reaches a different part of the site.

CredentialWhat WordPress documents about itReach through Ryze AI
Application password (self-hosted site)Part of WordPress core since version 5.6. It is created and revoked on the Edit User screen, has 24 characters, goes with the username as Basic Auth over HTTPS and does not work at wp-login.php. WordPress lists narrower passwords as a future feature, so each one carries its user's full access today.Any REST route the site offers, plugin routes included. The plugin, bridge and head-code tools need an administrator's password.
WordPress.com sign-in (WordPress.com and Jetpack sites)WordPress.com's OAuth2 endpoints serve its own sites and Jetpack-connected ones alike. On a Jetpack site the JSON API passes authenticated REST requests from WordPress.com to the live site.The core /wp/v2 routes only. In the test the plugin route /yoast/v1 answered not found.

Roles and what they mean for OpenClaw

A password carries its user's access, so that user's WordPress role is the real limit on an OpenClaw agent. Here is how WordPress describes the five standard roles and what each means for requests from OpenClaw.

WordPress roleWhat WordPress lets the role doFor requests from OpenClaw
AdministratorEvery administration feature of one site, activate_plugins among them. On a single-site install also install_plugins, update_plugins, delete_plugins, edit_users and unfiltered_html; on Multisite only the Super Admin has thoseThe role for plugin installs, both SEO bridges, head code and the plugin list on a self-hosted connection
EditorPublishes and manages posts, including other users' postsEdits and deletes any user's posts. Plugin, bridge and head-code jobs need an administrator
AuthorPublishes and manages their own postsOnly that user's own posts can be created, changed or removed
ContributorWrites and manages their own posts but cannot publish themDrafts of that user's own posts, with publishing out of reach
SubscriberManages only their profile and holds the read capability aloneNo content changes at all

No role adds these: plugin installs, the SEO bridges, head code and plugin routes such as /yoast/v1 on a WordPress.com connection; plugins from a zip file or a URL, because only wordpress.org directory plugins install; robots.txt changes; Elementor text on a post type that does not expose meta._elementor_data; and Yoast or Rank Math fields sent without the bridge, which WordPress silently drops. A security plugin, firewall or host that blocks /wp-json requests stops the connection until those requests are allowed.

Sources: REST API authentication, application passwords guide, WordPress roles and capabilities, WordPress.com OAuth2, Jetpack JSON API. Checked November 14, 2026.

Removing access

To cut OpenClaw off, stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. Setting enabled: false on the entry hides its tools and keeps the entry. To end the site access itself, revoke the application password in WordPress (Users > Profile > Application Passwords) and use View on the WordPress card in Ryze AI to manage or remove the site.

What OpenClaw can do in WordPress

The Ryze AI connector exposes 9 WordPress tools: two read, six write and one delete. Each runs against the connected site, and every tool takes the workspace and an optional connection_id. Writes and deletes are separate tools, so a filter can treat them differently.

ToolTypeWhat it does
wordpress__readReadSends GET requests to the site's REST API for posts, pages, media, categories, tags, users, plugins and custom post types.
wordpress__search_contentReadSearches one text field, such as the raw content of a post, and returns matching lines with line numbers and context.
wordpress__writeWriteSends POST, PUT or PATCH requests that create or update resources, such as a new post or a changed page.
wordpress__edit_contentWriteMakes find-and-replace edits to a field such as content, excerpt or title and saves it without resending the whole text.
wordpress__deleteDeleteSends a DELETE request, for example to remove a post.
wordpress__installPluginWriteInstalls and activates a wordpress.org directory plugin on a self-hosted site.
wordpress__enableYoastRestBridgeWriteOne-time setup on a self-hosted Yoast SEO site that makes the Yoast title, meta description, focus keyword, canonical and noindex fields writable, using a Code Snippets plugin snippet.
wordpress__enableRankMathRestBridgeWriteOne-time setup on a self-hosted Rank Math site that makes the Rank Math title, description, canonical URL and focus keyword fields writable, using a Code Snippets plugin snippet.
wordpress__addHeadCodeWriteAdds an HTML block inside the head of every page on a self-hosted site, such as a tracking snippet, a pixel or a verification tag.

Some limits apply in every client, OpenClaw included. The tools work only while the Ryze AI workspace has an active plan or trial, WordPress.com connections reach only the core /wp/v2 routes, and only wordpress.org directory plugins can be installed. Plugin installs can crash a site, and the bridge and head-code tools default to installIfMissing false, with a description that asks for your explicit yes in chat before the Code Snippets plugin is installed.

Approvals and keeping the agent read-only

OpenClaw's docs describe prompts before each MCP call for Codex runs only. In the built-in runtime, MCP tools follow the usual tool profiles and tool policy: the coding and messaging profiles include them, the minimal profile hides them, and tools.deny with bundle-mcp switches them all off. Inside a chat, + > Plugins > Tool access lets you turn off single tools for that session. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals, and in Claude the write and delete tools can be set to Needs approval; neither applies inside OpenClaw.

To keep the agent from changing the site, hide the write and delete tools with a toolFilter on the entry. Names are exact or simple * globs. Run openclaw mcp doctor ryze --probe first to see the names OpenClaw reports.

ryze: { url: "https://connector.get-ryze.ai/mcp", transport: "streamable-http", auth: "oauth", toolFilter: { exclude: [ "*wordpress__write", "*wordpress__edit_content", "*wordpress__delete", "*wordpress__installPlugin", "*wordpress__enableYoastRestBridge", "*wordpress__enableRankMathRestBridge", "*wordpress__addHeadCode", ], }, }

This entry hides the seven tools that change a site, so wordpress__read and wordpress__search_content stay. The patterns name these seven tools only; tools for other connected platforms stay visible.

Limits in numbers

LimitNumber
Records per REST requestper_page accepts a whole number from 1 to 100. The posts route returns 10 when it is unset. Bigger sets take more requests with page or offset.
Counting a collectionA paged answer carries X-WP-Total (the record count) and X-WP-TotalPages. The read tool's answers in the test carried total and totalPages fields.
Trimming an answer_fields keeps only the fields you name. Nested names such as meta.one-of-many-keys work since WordPress 5.3.
Application password24 characters of upper-case letters, lower-case letters and digits. A Last Used column is accurate to within 24 hours.
Trash after a deleteA self-hosted site empties trashed posts, pages, attachments and comments after 30 days by default (EMPTY_TRASH_DAYS). WordPress.com keeps deleted posts and pages in the trash for 30 days, while deleted media, categories and tags are gone at once.
Yoast SEO's REST APIRead only, with no POST or PUT calls, which is why writes need the bridge. It adds yoast_head and yoast_head_json to core answers.
OpenClaw request time60 seconds per MCP request by default, and 10 seconds to list tools at session start when requestTimeoutMs is not set.
OpenClaw tools and serversOpenClaw's pages state no maximum number of MCP servers or of tools per server. They do state runtime caps: 256 runtimes per Gateway and 448 MCP child processes.

Sources: REST API pagination, posts reference, global parameters, wp-config.php settings, WordPress.com MCP support, Yoast REST API. Checked November 14, 2026. OpenClaw limits from OpenClaw MCP documentation, checked November 15, 2026.

What the connector returned, tested

These are the nine wordpress__read calls behind this guide, sent through the Ryze AI connector on November 14, 2026 from a signed-in MCP client, Claude Code. The site was linked with a WordPress.com sign-in. Two calls read the site's schema and the other seven were built to fail so that the exact answers could be recorded.

CallWhy it was sentWhat came back
GET /wp/v2/typesList the content types the site hasWorked: 18 post types, among them post, page, attachment and wp_block
GET /wp/v2/taxonomiesList the ways content is groupedWorked: 6 taxonomies, among them category and post_tag
GET /wp/v2/posts/999999999Ask for a post ID that does not existnot_found: Invalid post ID.
GET /wp/v2/no-such-routeCall a route the site does not havenot_found: No route was found matching the URL and request method.
GET /wp/v2/types/not_a_typeAsk for a post type nobody registerednot_found: Invalid post type.
GET /wp/v2/posts, per_page 101Go one past the page size ceilingHTTP 400, rest_invalid_param: Invalid parameter(s): per_page
GET /wp/v2/posts, orderby no_such_fieldSort by a field that does not existHTTP 400, rest_invalid_param: Invalid parameter(s): orderby
GET /wp/v2/types with a bodySend a read the tool should rejectStopped by the connector before WordPress was called: invalid_arguments
GET /yoast/v1Reach a plugin namespace over a WordPress.com connectionnot_found: No route was found matching the URL and request method.

First 3 prompts to run

1. Review recent posts and drafts

List my 10 most recent WordPress posts with title, status, publish date and category, then show which of them are still drafts.

Tools used: wordpress__read on posts

What comes back: A list drawn from your own site with the fields you named. Nothing on the site is changed, and this page shows no sample output because none was run in OpenClaw.

2. Fix a phrase in one post

Search the post about our pricing for the old plan name, show me the matching lines, then replace it with the new name in that post only.

Tools used: wordpress__search_content, wordpress__edit_content

What comes back: The matching lines with line numbers and context, then a targeted edit saved without resending the whole post. This one changes the site.

3. Create a draft page

Create a draft WordPress page called Contact with a short intro paragraph and our support email address. Do not publish it.

Tools used: wordpress__write

What comes back: A new page created through the REST API with the status you asked for, which you can open in wp-admin to review.

None of the three prompts was run for this guide, and each answer comes from your own site. The agent uses the primary site unless you name another. On a self-hosted site with Yoast SEO or Rank Math you can also ask it to enable the one-time bridge and then update SEO titles and meta descriptions.

10 jobs to hand to OpenClaw

Ten jobs to give an OpenClaw agent, each with its Ryze AI tool. Only the type and taxonomy reads in the second job were run, from Claude Code and not OpenClaw. The other nine follow the tool descriptions and were not run.

JobAsk OpenClawToolWorks on the default connection
Post reviewList my 20 newest posts with title, status, publish date and category.wordpress__readYes, on either connection. Up to 100 posts per request
Content typesWhich post types and taxonomies does this site have? Then list the items of the type I pick.wordpress__readYes, on either connection. The type list was read in the test
Find a phraseShow every line in the post with the slug spring-sale that mentions the old price.wordpress__search_contentYes, on either connection
Swap a phraseReplace that phrase with the new wording in that post only, and show the line before and after.wordpress__edit_contentYes, unless you filtered the tool out and if the user may edit the post
New draftCreate a draft post with this title and outline, and leave it unpublished.wordpress__writeYes, unless you filtered the tool out
Post detailsMove these posts into the Tutorials category, tag them setup and shorten their excerpts.wordpress__writeYes. The same tool creates and renames categories and tags
Image alt textList the images in the media library, then set the alt text I give you on the ones I name.wordpress__read, wordpress__writeYes, on either connection
Remove a postDelete the draft post with the ID I give you.wordpress__deleteYes, if the role allows it. Consider filtering this tool out
Yoast or Rank Math fieldsTurn on the Yoast bridge, then set the SEO title and meta description of this post.wordpress__enableYoastRestBridge or wordpress__enableRankMathRestBridge, then wordpress__writeNo. Self-hosted site and an administrator's application password only, after your yes in chat
Head codeAdd this site verification tag to the head of every page.wordpress__addHeadCodeNo. Self-hosted site and an administrator's application password only, after your yes in chat

Elementor page text can be reached only where the post type exposes meta._elementor_data, and robots.txt is outside what the agent changes, so use wp-admin for those.

6 ways to connect OpenClaw to WordPress

Six ways can give an OpenClaw agent access to a WordPress site. This guide treats the first, the Ryze AI connector, as the main way: it is a hosted address, so nothing runs on the Gateway host or inside WordPress, and one address covers self-hosted, WordPress.com and Jetpack sites. The other five were checked on the dates in the sources. None of them was run inside OpenClaw, and only AI Engine names OpenClaw on its own page.

WayRuns whereSetup in OpenClawWhat it reaches in WordPressPrice
Ryze AI connector (the main way)Hosted. One address for every useropenclaw mcp set, the Control UI or openclaw.json, then openclaw mcp login ryzeSelf-hosted, WordPress.com and Jetpack sites. 9 tools to read, search, create, edit and delete content, plus plugin installs, SEO bridges and head code on self-hosted sitesSEO Starter is $129 per month with a 3-day free trial
WordPress.com MCP serverHosted by WordPress.com at https://public-api.wordpress.com/wpcom/v2/mcp/v1Save the address as a remote server. Sign-in is OAuth 2.1 with PKCE and dynamic client registration, with a choice of Full access, Read only or Keep existing access. WordPress.com's pages name other clients, and OpenClaw's docs do not say whether it tries dynamic registration first, so the pairing is unverifiedEvery site on the WordPress.com account and self-hosted sites linked through Jetpack, within the user's role. New posts start as draftsIncluded on paid WordPress.com plans and with Jetpack AI or Complete. Free sites, and Jetpack sites without those plans, through November 30, 2026
AI Engine plugin by Meow AppsOn your WordPress site, as a pluginThe plugin page names OpenClaw among the assistants. Its setup steps for OpenClaw were not opened, so the entry would be a remote server pointing at the site and is unverifiedMore than 140 tools as the vendor states it: posts, pages, media, comments, users, taxonomies, menus and fields of the installed SEO plugin. Changes are recorded and can be undone, with history kept 30 daysThe MCP server is in the free plugin. Pro is from $59 per year
MCP Adapter plugin (official, on your site)On the WordPress siteInstall the plugin (WordPress 6.9 and PHP 7.4 or newer), then save the site's /wp-json/mcp/mcp-adapter-default-server endpoint as a remote server with an Authorization: Basic header built from a username and application password. The plugin's guides name Claude Desktop, Claude Code, VS Code and Cursor, so OpenClaw is unverifiedOnly abilities registered through the Abilities API and marked public, reached through 3 meta-tools. The plugin has no content tools of its ownFree, GPL-2.0-or-later
Zapier MCPHostedOn Zapier's WordPress page generate a server address and pick the actions, then save that address as a remote server. Zapier's pages name other clients, so the OpenClaw entry is yours to writeThe actions you switch on, such as Create Post, Update Post, Upload Media and Find PostTwo tasks from your Zapier plan per successful tool call
ComposioHostedStart a session in Composio's SDK with the wordpress_com toolkit and MCP on, then save the address and headers it returns. WordPress.com connections first need an OAuth app of your ownWordPress.com accounts, through 26 tools for posts, pages, media, menus, templates, settings and stats. No toolkit page for self-hosted WordPress was foundThe free plan stops at 10,000 app tool calls a month. Standard is $18 per seat per month

Options that do not fit this job

  • WordPress Studio MCP server. It runs on your computer from the Studio desktop app and works on local Studio sites. Studio's page names other clients and describes no route to a live self-hosted site.
  • Automattic's mcp-wordpress-remote proxy. A local stdio bridge to WordPress MCP endpoints. OpenClaw supports stdio servers, but the README names Claude Desktop and Claude Code and says a client that can reach the endpoint over streamable HTTP does not need the proxy.
  • InstaWP/mcp-wp and docdyhr/mcp-wordpress. Open-source Node servers that sign in with an application password. Their READMEs name Claude Desktop, VS Code and Cline, and neither names OpenClaw.
  • WordPress Playground MCP server. It drives a Playground instance in a browser tab instead of a live site, and its announcement names Claude Code, Codex and Claude Desktop.
  • WordPress Agent Skills. The skills teach WordPress development patterns and give no access to a site or its data.
  • Automattic/wordpress-mcp. The earlier plugin is retired, and WordPress.com's landing page says it is being replaced by the MCP Adapter.
  • WordPress 7.0's AI Client and Connectors screen. They let plugins on a site call AI providers. They point out of WordPress toward a model, so they give OpenClaw no way into the site.
  • ClawHub. OpenClaw's public plugin registry has no Ryze AI plugin, so the connector is saved by address as in the steps above.

Which one to pick

Ryze AI is the best way to connect OpenClaw to a self-hosted WordPress site for post, page and SEO-field edits behind one sign-in, with these caveats: the plugin, bridge and head-code tools need an administrator's application password and do not run over WordPress.com connections, and it needs a Ryze AI plan. For a site on WordPress.com the WordPress.com MCP server needs no Ryze AI plan and offers a Read only level, but OpenClaw is not named on its pages. Pick AI Engine when you want a tool set that lives inside the site and its page names OpenClaw. Pick the MCP Adapter when developers want to decide, ability by ability, what the agent may run. Zapier and Composio suit teams that already route other apps through them.

Sources: WordPress.com MCP developer page, WordPress.com MCP support, WordPress.com AI and MCP, AI Engine, MCP Adapter plugin, MCP Adapter on GitHub, MCP on WordPress Studio, Zapier WordPress MCP, Zapier MCP quickstart, Composio WordPress.com toolkit, Composio pricing, mcp-wordpress-remote, InstaWP/mcp-wp, docdyhr/mcp-wordpress, Playground MCP announcement, WordPress Agent Skills, WordPress 7.0 announcement (all opened November 14, 2026), OpenClaw ClawHub (opened November 15, 2026), Ryze AI WordPress guide.

OpenClaw, WordPress and MCP: dates that matter

DateWhat happened
November 5, 2020WordPress published the application passwords integration guide for version 5.6, the release that put them into core.
March 20, 2026WordPress.com's MCP server gained write tools across posts, pages, comments, categories, tags and media.
March 31, 2026OpenClaw 2026.3.31 added remote HTTP and SSE servers by URL under mcp.servers, with auth headers and an optional streamable-http transport.
May 20, 2026WordPress 7.0, named Armstrong, was released.
August 31, 2026OpenClaw 2026.8.1, also called OpenClaw 2.0, added servers from the chat composer and per-requester OAuth for shared MCP servers.
September 23, 2026OpenClaw 2026.9.6 let administrators sign in to MCP connectors from Settings.
October 2, 2026MCP Adapter 0.7.0 came out, and the plugin joined the wordpress.org plugin directory that day.
November 3, 2026OpenClaw 2026.10.10 began protecting MCP configuration while the Gateway runs, so openclaw mcp set and login need the Gateway stopped. The same day WordPress.com opened MCP access to free sites for a limited time.
November 10, 2026OpenClaw 2026.11.3 came out. On November 15, 2026 it was the newest stable release, and its notes list no MCP change.
November 30, 2026Last day of MCP access for free WordPress.com sites and for Jetpack sites without a Jetpack AI or Complete plan.

Sources: application passwords guide, WordPress.com, March 20, 2026, WordPress 7.0, MCP Adapter releases, MCP Adapter plugin, WordPress.com, November 3, 2026, WordPress.com MCP developer page, OpenClaw releases, OpenClaw 2026.3.31 changelog, OpenClaw 2026.10.10 release notes. Checked November 15, 2026 and November 14, 2026.

How this guide was tested

Two sets of checks stand behind this guide: the connector and a WordPress site on November 13 and 14, 2026, and OpenClaw's documentation on November 15, 2026. The table lists what was run and what came back.

What was runWhat came back
The connector address, called without a sign-in (November 13)HTTP 401. OpenClaw's docs say a Streamable HTTP server that answers initialization with 401 is how a server asks for a sign-in.
The WordPress tool list (November 14)All 9 names in the tools table above loaded from the live connector, and each returned a definition.
Schema reads with wordpress__read (November 14)A site linked through a WordPress.com sign-in reported 18 post types and 6 taxonomies.
Six reads built to fail (November 14)Five answers came from WordPress and one from the connector, which refused a read that carried a body. The messages are in the errors table below.
A plugin route over a WordPress.com connection (November 14)/yoast/v1 came back as not found, in line with the rule that such connections reach only the /wp/v2 routes.
Total9 wordpress__read calls through the connector.

Not run for this page: every step inside OpenClaw. No Gateway was installed or started, no server was saved and no sign-in was attempted. The OpenClaw steps follow its documentation and changelog as read on November 15, 2026. The signed-in client for the tool list and the reads was Claude Code, which reaches the same server and the same nine tools. No self-hosted site was linked, so no application password was used. No read returned posts, pages, media, users or plugins, and nothing that changes a site was run: the write, edit, delete, plugin-install, bridge and head-code tools were left alone.

OpenClaw and WordPress errors and fixes

Exact error messages

WordPress and the connector sent these messages back in the test on November 14, 2026, over a WordPress.com connection, and the first row is an OpenClaw message taken from its documentation, not seen in a run. The last WordPress row uses a punctuation mark this site does not print, so it is described in words.

MessageWhat it meansWhat to do
authentication refused (401)OpenClaw's docs say this appears in the startup log and catalog diagnostic when a Streamable HTTP server answers initialization with HTTP 401, which is how a server asks for a sign-in.Run openclaw mcp login ryze with the Gateway stopped, or click Sign in under Settings > MCP.
Invalid post ID.The connected site has no post with that ID.Ask the agent to list posts first and take an ID from that list.
No route was found matching the URL and request method.The path is not on this site, or it is a plugin route such as /yoast/v1 over a WordPress.com connection.Check the path against /wp/v2/types. Plugin routes need a self-hosted connection.
Invalid post type.No post type with that slug is registered on the site.Read /wp/v2/types and use one of the slugs it returns.
Invalid parameter(s): per_pageThe request asked for 101 items in one page, and WordPress accepts 1 to 100. Code rest_invalid_param, HTTP 400.Ask for 100 or fewer and page through the rest.
Invalid parameter(s): orderbyThe sort field does not exist. For posts the REST API handbook lists date, relevance, id, include, title and slug. Code rest_invalid_param, HTTP 400.Sort by one of those fields.
invalid_arguments, about a GET request with a body (described, not quoted)The read tool refuses a GET request that carries a body and points to the query field for filters. WordPress is never called.Send the same read again with the filters in query.

Other problems

The WordPress tools do not appear in OpenClaw
Until shared credentials exist, OpenClaw leaves the server out of the agent runtime instead of failing the turn. Run openclaw mcp login ryze with the Gateway stopped, then check with openclaw mcp status or openclaw mcp doctor ryze --probe. If you saved the connector before the site was linked in Ryze AI, remove the entry and save it again.
The tool list is empty or times out
The tool list at session start gets 10 seconds when requestTimeoutMs is not set. Raise requestTimeoutMs on the entry, and confirm transport is streamable-http, because OpenClaw reads a missing transport as sse.
The sign-in page opens on the wrong machine
Approve it in the browser, then give the code it returns to openclaw mcp login ryze with --code.
The API key is ignored
Static Authorization headers are ignored while auth: "oauth" is on. Remove auth for the key route, or remove the header and use OAuth.
An openclaw mcp command holds back
Since OpenClaw 2026.10.10 (November 3, 2026), commands that change saved servers, and login, need the Gateway stopped. Stop it, run the command and start it again, or edit openclaw.json, or use Settings > MCP.
Ryze AI says the credentials are wrong
Use the username you type at wp-admin, a Site URL that starts with https://, and the application password exactly as WordPress showed it. A lost password cannot be viewed again, so create a new one.
Users > Profile has no Application Passwords area
By default WordPress offers the feature only on HTTPS sites, and it can be switched off for the whole site or for some users. Ask whoever manages the site to turn it on.
Connecting stops at a firewall or security message
A security plugin, web application firewall or host rule that blocks /wp-json requests prevents the connection. Allow those requests and connect again.
A Jetpack site will not connect
Enable the Jetpack JSON API module on the site, then sign in with WordPress.com again.
The plugin, bridge or head-code tools refuse
They need a self-hosted connection and an administrator user. On WordPress.com connections, change those settings in wp-admin.
Yoast or Rank Math values are ignored
WordPress silently drops those fields when they are sent through the plain REST API. Run the Yoast or Rank Math bridge first, on a self-hosted site.
The tools reply that a subscription is required
The WordPress tools need an active Ryze AI plan or free trial. Start the trial, then retry.

Terms on this page

MCP
The Model Context Protocol, an open standard for connecting AI applications to outside systems. OpenClaw, Claude and ChatGPT support it.
Gateway
The OpenClaw process that runs your agents and keeps their settings, MCP servers and saved sign-ins.
openclaw.json
The JSON5 settings file at ~/.openclaw/openclaw.json. MCP servers live under mcp.servers.
Application password
A 24-character password WordPress makes on a user's profile for programs that call the REST API. It can be revoked on its own and does not work at wp-login.php.
REST API
WordPress's built-in HTTP interface under /wp-json. Core content sits in the /wp/v2 routes: posts, pages, media, categories, tags and users.
Role and capability
A role such as Editor bundles capabilities such as publish_posts or activate_plugins. The connection can do only what its user's role allows.
Jetpack connection
The link between a self-hosted site and a WordPress.com account. Its JSON API forwards authenticated REST requests from WordPress.com to the site.

Source for MCP: modelcontextprotocol.io. Checked November 15, 2026.

Frequently asked questions

How do I connect OpenClaw to WordPress?

The main way is the Ryze AI connector. Link your site in Ryze AI under Integrations with an application password (self-hosted) or a WordPress.com sign-in. Then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using openclaw mcp set, Settings > MCP or openclaw.json, and sign in with openclaw mcp login ryze.

Is there a WordPress MCP server for OpenClaw?

Yes. The Ryze AI connector is one: its address is https://connector.get-ryze.ai/mcp and it has 9 WordPress tools. WordPress.com also runs its own server at https://public-api.wordpress.com/wpcom/v2/mcp/v1, WordPress publishes the MCP Adapter plugin for self-hosted sites, and the AI Engine plugin names OpenClaw on its page.

What is the WordPress MCP server URL for OpenClaw?

For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. WordPress.com's own address is https://public-api.wordpress.com/wpcom/v2/mcp/v1. A self-hosted site with the MCP Adapter plugin serves /wp-json/mcp/mcp-adapter-default-server on its own domain.

Which should I use, Ryze AI or the WordPress.com server?

Use the Ryze AI connector for a self-hosted site, where the plugin, SEO-bridge and head-code tools apply. A site on WordPress.com can use the WordPress.com server directly, which has a Read only access level, though none of its pages opened on November 14, 2026 names OpenClaw and that pairing was not run.

Do I need a WordPress.com site or will self-hosted work?

Both work in Ryze AI. A self-hosted site connects with its URL, an admin username and an application password. A WordPress.com or Jetpack site connects with a WordPress.com sign-in, and Jetpack sites need the JSON API module enabled.

Which OpenClaw plan do I need?

None. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier. The model provider your agent uses has its own costs, which are outside this guide.

Can OpenClaw edit or delete WordPress content?

Yes. Through Ryze AI an agent can create, update and delete posts, pages, media, categories, tags and custom post types, and make targeted text edits, within the rights of the WordPress user behind the credential.

Does OpenClaw ask before it changes a post?

OpenClaw's docs describe per-call prompts for Codex runs only. In the built-in runtime, MCP tools follow tool profiles and policy. To require a pause before changes, hide the write and delete tools with a toolFilter and enable them only when you want a change made.

Can OpenClaw change Yoast SEO or Rank Math fields?

On self-hosted sites, yes, after a one-time bridge for Yoast or Rank Math that needs your explicit yes in chat. On WordPress.com connections the bridges do not work, so those fields are edited in wp-admin.

Can I connect more than one WordPress site?

Yes. Click View on the WordPress card in Ryze AI and choose Add one more account. The agent uses the primary site unless you name another, and the tools accept an optional connection_id. How several sites interact with the one-website rule of an SEO plan is not documented, so ask Ryze AI support before relying on it.

Why do the WordPress tools not show up in OpenClaw?

Until shared credentials exist, OpenClaw leaves the server out of the agent runtime. Run openclaw mcp login ryze with the Gateway stopped. If you linked the site in Ryze AI after saving the server, remove the ryze entry and save it again so the tool list refreshes.

Is there an AI SEO tool that connects straight to my WordPress site?

Yes, Ryze AI SEO links to the WordPress site itself: Content Plan articles publish there as posts, and Technical Audit Fix with agent applies fixes on the site. Through the connector an OpenClaw agent reaches the same site to read and edit content.

Can I fix image alt text in WordPress without exporting the media library?

Yes. Through the connector an agent can list media library items and set alt text on the ones you name with wordpress__write. Ask it to list the images first, agree on the text, then run the update. This was not run in OpenClaw.

What is a good way to publish programmatic SEO posts to WordPress in bulk?

Publish from a plan that writes straight to the site: Ryze AI SEO's Content Plan posts articles to the connected WordPress site, up to 90 per billing cycle and up to 3 a weekday on SEO Starter, in Automatic or Manual publishing mode. An OpenClaw agent can also create draft posts one at a time with wordpress__write for review in wp-admin.

How much does it cost to connect OpenClaw to WordPress?

Adding the connector costs nothing, but the WordPress tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, and annual billing takes 30% off the first year.

How do I disconnect WordPress from OpenClaw?

Stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. To end the site access, revoke the application password under Users > Profile and manage the site on its Ryze AI card.

Connect WordPress to OpenClaw

Your site connects once in Ryze AI, then your OpenClaw agent reads, creates and edits posts, pages and media. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year.

WordPress MCP server

Need help? Read the Ryze AI help center page for WordPress or email Ryze AI support.