By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Hermes Agent to WordPress is the Ryze AI connector. Connect your site in Ryze AI with an application password or a WordPress.com sign-in, add a ryze entry with the URL https://connector.get-ryze.ai/mcp and auth: oauth under mcp_servers in ~/.hermes/config.yaml, then run hermes mcp login ryze and click Allow connection. Start a new session and ask about your posts.
- In Ryze AI open Integrations, click Connect on WordPress and enter the site URL, username and an application password (or sign in on WordPress.com)
- Add the ryze entry to mcp_servers in ~/.hermes/config.yaml
- Run hermes mcp login ryze and click Allow connection
- Start a new session or run /reload-mcp, then ask your first WordPress question
Hermes Agent to WordPress at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a remote HTTP MCP server that Hermes Agent reads from one ryze entry under mcp_servers in ~/.hermes/config.yaml |
| Connector address | https://connector.get-ryze.ai/mcp, identical for every user |
| How Hermes Agent signs in | OAuth with auth: oauth, completed once with hermes mcp login ryze. A Ryze AI API key sent as a bearer header from ~/.hermes/.env is the alternative |
| What WordPress needs | Self-hosted site: the site URL, an admin username and an application password. WordPress.com or Jetpack site: a one-click WordPress.com sign-in |
| WordPress tools | 9 in total: 2 that read or search, 6 that write or set up, and 1 that deletes. Listed in the tools table below |
| Changes to the site | Yes, through the write, edit and delete tools, within the role of the WordPress user that is connected. Setting trust: untrusted on the ryze entry makes Hermes Agent ask before write-capable calls |
| Hermes Agent plan | None. Hermes Agent is open source under the MIT license per its GitHub repository and runs on your own machine or server |
| Ryze AI price | SEO Starter costs $129 per month after a 3-day free trial. Adding the connector costs nothing |
| WordPress's own option | WordPress.com runs a hosted MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1, and self-hosted sites can use the MCP Adapter plugin. Neither WordPress page read for this guide names Hermes Agent by name |
| Last tested | Read calls through the connector were run on November 14, 2026 from Claude Code on a WordPress.com connection. The steps inside Hermes Agent were not run |
Before you start
- Hermes Agent installed. It is open source from Nous Research, licensed MIT per its GitHub repository, and self-hosted, so there is no plan tier to buy. The configuration lives in ~/.hermes/config.yaml.
- A WordPress user you can connect with. On a self-hosted site that is the username you sign in to wp-admin with, plus an application password from Users > Profile. On a WordPress.com or Jetpack site it is a WordPress.com sign-in, and Jetpack sites need the Jetpack JSON API module on. Plugin installs, 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 and includes publishing Content Plan articles to the site. Connecting the connector is free, but the WordPress tools need any active Ryze AI plan or trial.
How to connect Hermes Agent to WordPress with OAuth
The first step happens in WordPress and Ryze AI, the rest in Hermes Agent. The connector URL is the same for every user.
Connect your site in Ryze AI
For a self-hosted site, open Users > Profile in WordPress admin, scroll to Application Passwords, enter the name Ryze AI, click Add New Application Password and copy it, because it is shown once. In Ryze AI open Integrations, click Connect on the WordPress card, pick the Self-hosted site tab, enter the Site URL, your username and the application password, then click Continue. For a WordPress.com or Jetpack site, pick that tab and sign in on WordPress.com instead.
Add the ryze entry to config.yaml
Open ~/.hermes/config.yaml and add a ryze server under mcp_servers. Editing the file inside a running session starts an automatic MCP reload with a 30-second timeout, which is too short for a browser sign-in, so add the entry and then run the login in the next step.
mcp_servers: ryze: url: "https://connector.get-ryze.ai/mcp" auth: oauthSign in to the connector
Run hermes mcp login ryze. Hermes Agent prints an authorize URL and opens your browser when it can. Sign in on the Ryze AI page, choose the workspace and click Allow connection. Hermes Agent caches the tokens at ~/.hermes/mcp-tokens/ryze.json and reuses them until a refresh fails.
Load the tools
Start a new session, or run /reload-mcp inside a running one. Hermes Agent registers each tool under the name mcp_<server>_<tool>, so the WordPress tools start with mcp_ryze_. To see what the server answers, run hermes mcp test ryze.
Ask your first question
Ask: List my 10 most recent posts with their title, status, date and categories.
The Ryze AI help center page for WordPress covers the WordPress side of the connection, and the Ryze AI help article on API keys and the MCP endpoint covers the connector URL. The Ryze AI developers page lists the same URL.
Source for the Hermes Agent steps: Hermes Agent MCP documentation, opened November 21, 2026.
API key, tool filters and headless hosts
Hermes Agent keeps every MCP server in one file, ~/.hermes/config.yaml. These are the variations that matter for this connector.
A Ryze AI API key instead of OAuth
Create a key in Ryze AI under Workspace Settings > Profile > API keys > Create key and copy it, because it is shown once. Put RYZE_API_KEY with the rk_live_ key in ~/.hermes/.env and reference it in the header, since Hermes Agent resolves ${VAR} placeholders in headers from environment variables. Run /reload-mcp afterwards. The WordPress site stays connected inside Ryze AI, so no WordPress credential is stored in Hermes Agent.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
headers:
Authorization: "Bearer ${RYZE_API_KEY}"Show Hermes Agent only the read tools
Each server entry accepts tools.include and tools.exclude. This entry registers the two WordPress read tools and nothing else from the connector, which also hides the tools of every other platform in the workspace. It hides tools from Hermes Agent only. The access of the connected WordPress user is unchanged.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
tools:
include:
- wordpress__read
- wordpress__search_contentA remote or headless host
When Hermes Agent runs on a server and your browser is on another machine, the local callback cannot reach the browser. The Hermes Agent documentation says to paste the redirect URL back at the prompt, or to add --flow device for device-code authorization when the server supports it. Whether the Ryze AI connector supports device-code authorization was not checked, so the paste route and the API key are the ones to try first.
hermes mcp login ryzeThe messaging gateway and unattended runs
A running gateway never opens a browser, so sign in with hermes mcp login ryze first. A server whose first connect failed because no token was cached waits for a login.
Reloading and timeouts
The Hermes Agent page read for this guide gives no default for the length of a tool call. Hermes Agent waits for the browser sign-in for 5 minutes, and oauth.timeout on the entry makes it wait longer. connect_timeout on the entry bounds the first connection. WordPress returns at most 100 records per request, so a long list of posts comes back in pages.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
oauth:
timeout: 600
connect_timeout: 60Hermes Agent and MCP: the facts in one table
| Topic | What the Hermes Agent documentation says |
|---|---|
| Where servers are added | ~/.hermes/config.yaml under mcp_servers, or with hermes mcp install for the catalog of Nous-approved servers |
| Transports | Local stdio servers (command and args) and remote HTTP servers (url) |
| Sign-in | auth: oauth does the browser sign-in. Hermes Agent identifies itself with a Client ID Metadata Document on servers that support one and falls back to dynamic client registration on those that do not. Static bearer headers also work |
| Token storage | ~/.hermes/mcp-tokens/<server>.json, written with 0600 permissions and reused until refresh fails |
| Tool names | mcp_<server_name>_<tool_name>, so a server named ryze registers its tools under names that start with mcp_ryze_ |
| Approval | Set trust: untrusted on a server entry that needs approval |
| Filtering | tools.include and tools.exclude per server. hermes mcp configure opens a checklist of the tools |
| Reload | /reload-mcp, then hermes mcp test <server> to see what the server answers. Editing config.yaml inside a running CLI session reloads MCP with a 30-second timeout |
| Proxies | HTTP servers honor HTTPS_PROXY, HTTP_PROXY and NO_PROXY |
| Plan | None. Open source, self-hosted |
Sources: Hermes Agent MCP documentation, NousResearch/hermes-agent on GitHub. Opened November 21, 2026.
Other clients
The same URL works in other MCP clients. The site is connected once in Ryze AI, so nothing changes on the WordPress side.
Claude Code
Run claude mcp add --transport http ryze https://connector.get-ryze.ai/mcp, then sign in from /mcp. The site is connected once in Ryze AI, so the WordPress side does not change from client to client.
Claude and ChatGPT
In Claude open Customize > Connectors, choose Add custom connector and enter https://connector.get-ryze.ai/mcp. In ChatGPT the full custom MCP flow is for Business and Enterprise/Edu plans, and Pro users get read and fetch permissions only. A connection link from Claude or ChatGPT opens a page for the site URL, username and application password.
Codex and Cursor
Codex takes codex mcp add ryze --url https://connector.get-ryze.ai/mcp. Cursor reads the same URL from its mcp.json file. The Ryze AI developers page has the matching config for each.
Access and Hermes settings
Two sign-ins are involved: the WordPress credential that Ryze AI holds, and Ryze AI for the connector. Three things decide what Hermes Agent can reach.
- Which site
- The primary site, unless you name another. A workspace can hold several WordPress sites with View > Add one more account, and the tools accept an optional connection_id.
- What Hermes Agent can change
- Whatever the connected WordPress user may do. An application password acts with its user's own access, so a Contributor connection cannot publish and an Administrator connection can install plugins.
- What Hermes Agent asks first
- The trust, tools.include and tools.exclude settings on the ryze entry decide which tools Hermes Agent sees and when it asks first. They are client-side settings and do not change what the WordPress user may do.
The WordPress access Ryze AI uses
WordPress has no app scopes on the self-hosted route: the application password carries its user's role. The table lists the roles from WordPress's roles page and what each means for this connection.
| Role or credential | What WordPress says it covers | What Hermes Agent gets |
|---|---|---|
| Administrator | All administration features within a single site, including activate_plugins | Everything below, plus plugin installs, the Yoast and Rank Math bridges and head code on a self-hosted site |
| Editor | Publish and manage posts, including other users' posts | Read, create, edit and publish content across authors |
| Author | Publish and manage their own posts | Work on that user's own posts |
| Contributor | Write and manage their own posts but cannot publish them | Drafts only. A request to publish is refused by WordPress |
| Application password | 24 characters, generated on the user profile, sent over Basic Auth on https, revocable on its own, cannot log in at wp-login.php | The access of the user it belongs to, with no narrower scope |
| WordPress.com sign-in | OAuth2 sign-in on WordPress.com for WordPress.com and Jetpack sites | Core /wp/v2 routes only. The scope Ryze AI requests is not listed in the sources used here |
Not part of a WordPress.com or Jetpack connection: plugin installs, the Yoast and Rank Math bridges and head code. Plugin routes such as /yoast/v1 need a self-hosted connection. Only wordpress.org directory plugins can be installed, not zip files or URLs, and robots.txt is outside what the agent changes.
Application passwords are shown once when created. Pick a name such as Ryze AI so that you can find and revoke it later on the same profile page. A security plugin, firewall or host that blocks /wp-json requests stops the connection until those requests are allowed.
Sources: Application Passwords integration guide, roles and capabilities, WordPress.com OAuth2. Checked November 14, 2026.
Removing access
To remove access, click View on the WordPress card in Ryze AI and disconnect the site, or revoke the application password on the user's profile. In Hermes Agent, set enabled: false on the ryze entry or delete it from config.yaml, and delete ~/.hermes/mcp-tokens/ryze.json to drop the cached tokens.
What Hermes Agent can do in WordPress
The Ryze AI connector exposes 9 WordPress tools: 2 read or search, 6 write or setup, and 1 delete. In Hermes Agent the names appear with the mcp_ryze_ prefix.
| Tool | Type | What it does |
|---|---|---|
| wordpress__read | Read | Runs a read-only (GET) WordPress REST API request on the connected site, covering posts, pages, media, categories, tags, users, plugins and custom post types. |
| wordpress__search_content | Read | Searches a text field such as a post's raw content and returns the matching lines with line numbers and context. |
| wordpress__write | Write | Runs a REST API request that creates or updates resources (POST, PUT or PATCH), such as creating a post or updating a page. |
| wordpress__edit_content | Write | Makes find-and-replace edits to a text field such as post or page content, an excerpt or a title, and writes it back without resending the whole content. |
| wordpress__delete | Delete | Runs a DELETE REST API request, for example to delete a post. |
| wordpress__installPlugin | Write | Installs and activates a plugin from the wordpress.org directory on a self-hosted site. Plugin installs can crash a site. |
| wordpress__enableYoastRestBridge | Write | One-time setup on a self-hosted Yoast SEO site that makes the Yoast title, meta description, focus keyword, canonical and noindex fields writable through the REST API. |
| wordpress__enableRankMathRestBridge | Write | One-time setup on a self-hosted Rank Math site that makes the Rank Math title, description, canonical URL and focus keyword fields writable through the REST API. |
| wordpress__addHeadCode | Write | Adds a block of HTML inside the head of every page on a self-hosted site, such as a tracking snippet, pixel or verification tag. |
Approvals in Hermes Agent
In Hermes Agent, the documentation says to set trust: untrusted on a server entry that needs approval. Add it to the ryze entry if you want a prompt before changes. The Yoast bridge, Rank Math bridge and head-code tools default to installIfMissing false and require your explicit yes in chat before the Code Snippets plugin is installed. Separately, the Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals, and scheduled tasks run without an approval step.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
trust: untrustedWordPress limits in numbers
WordPress figures in WordPress's own units, plus the Ryze AI tool input limits seen in the tool definitions on November 14, 2026.
| Limit | Number |
|---|---|
| Page size | per_page accepts 1 to 100. The posts reference gives a default of 10. Larger sets need several requests with page or offset |
| Paging totals | Responses carry X-WP-Total and X-WP-TotalPages headers |
| Field selection | _fields limits a response to named fields. Nested fields are supported since WordPress 5.3 |
| Request quota | No request quota figure appears on the REST API handbook pages or the WordPress.com MCP pages read for this guide. WordPress.com asks developers not to make excessive calls, without a number |
| Trash | Trashed posts, pages, attachments and comments are permanently deleted after 30 days by default. On WordPress.com deleted media, categories and tags are permanent |
| Search tool | search_content takes a pattern up to 500 characters and context_lines from 0 to 10, default 2 |
| Edit tool | edit_content takes 1 to 50 edits per call. old_string is up to 20,000 characters and new_string up to 100,000 |
| Head code | addHeadCode takes html up to 8,192 characters |
| Free WordPress.com sites | MCP access on free WordPress.com sites and on Jetpack sites without a Jetpack AI or Complete plan runs through November 30, 2026, per WordPress.com. That is WordPress.com's own MCP server, not a Ryze AI limit |
Sources: REST API pagination, global parameters, wp-config, WordPress.com MCP tools reference. Checked November 14, 2026.
Tested calls
Hermes Agent did not send these. On November 14, 2026 the same Ryze AI connector was called from Claude Code on a WordPress.com connection in a test workspace. All 9 tools were loaded by name and only reads were run. No site name, address or content was recorded.
| What was asked | What came back |
|---|---|
| wordpress__read on /wp/v2/types | Worked. 18 post types on that site |
| wordpress__read on /wp/v2/taxonomies | Worked. 6 taxonomies |
| wordpress__read on a post ID that does not exist | Refused with not_found and the message Invalid post ID. |
| wordpress__read on a route that does not exist | Refused with not_found and the message No route was found matching the URL and request method. |
| wordpress__read with per_page 101 | Refused with HTTP 400 and the code rest_invalid_param for per_page |
| wordpress__read on /yoast/v1 over the WordPress.com connection | Refused with not_found, as expected: WordPress.com connections reach only /wp/v2 routes |
The write, edit, delete, plugin, bridge and head-code tools were not run, because they change a site. No self-hosted connection with an application password was tested.
First 3 prompts to run
Each answer comes from your own site, so this page describes what comes back instead of showing sample numbers. Hermes Agent picks the tool itself; the names are listed so you can check which one ran.
1. Review recent posts
List my 10 most recent posts with their title, status, date and categories.
Tools used: wordpress__read
What comes back: A list of posts from your own site as plain text in Hermes Agent. Nothing in WordPress is changed.
2. Find a phrase in a long post
Search the content of the post with the slug I name here for the word pricing and show the matching lines with their line numbers.
Tools used: wordpress__read, wordpress__search_content
What comes back: Matching lines with line numbers and context from one post. It is a read, so nothing changes.
3. Fix one phrase in place
In the post with the slug I name here, replace the phrase old name with new name and leave the rest of the post alone.
Tools used: wordpress__read, wordpress__edit_content
What comes back: A changed post, because the edit is written back to the site. With trust: untrusted on the ryze entry, Hermes Agent asks before the write runs.
When you want a change, describe it in plain words. Replace the names in the prompts with ones from your site.
10 jobs to hand to Hermes Agent
Ten jobs you can give Hermes Agent, each beside the tool that does the work. The last column assumes a self-hosted connection with an administrator user, and says where a WordPress.com or Jetpack connection differs.
| Job | Ask Hermes Agent | Tool | On the default connection |
|---|---|---|---|
| Recent posts | List recent posts with title, status, date and category. | wordpress__read | Yes |
| Find a phrase | Find every line in a post or page that contains a phrase. | wordpress__search_content | Yes |
| Fix a phrase in place | Replace a phrase in one post without resending the whole post. | wordpress__edit_content | Yes |
| Draft a post or page | Create a draft post or page. | wordpress__write | Yes |
| Change post fields | Change a post's title, excerpt, status, categories or tags. | wordpress__write | Yes |
| Image alt text | Update image alt text and captions in the media library. | wordpress__write | Yes |
| Remove a post | Delete the test post I name here. | wordpress__delete | Yes, and trust: untrusted makes Hermes Agent ask before the call |
| Yoast SEO fields | Write the Yoast title, meta description, focus keyword, canonical or noindex. | wordpress__enableYoastRestBridge, then wordpress__write | Self-hosted administrator only, after a one-time bridge |
| Rank Math fields | Write the Rank Math title, description, canonical URL or focus keyword. | wordpress__enableRankMathRestBridge, then wordpress__write | Self-hosted administrator only, after a one-time bridge |
| Head tag | Add a tracking pixel or verification tag to the head of every page. | wordpress__addHeadCode | Self-hosted administrator only |
7 ways to connect Hermes Agent to WordPress
Seven ways to connect Hermes Agent to WordPress. This guide treats the Ryze AI connector as the main way: the site stays connected in Ryze AI, and Hermes Agent holds one address and a browser sign-in. Hermes Agent accepts any remote HTTP MCP server by url and any local server by command, and none of these routes was run in Hermes Agent.
| Way | Runs where | Setup in Hermes Agent | What it reaches in WordPress | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | A ryze entry with url and auth: oauth, then hermes mcp login ryze. Or a bearer header with a Ryze AI API key read from ~/.hermes/.env | 9 tools on the connected site, self-hosted or WordPress.com: REST reads and writes, content edits, deletes, and on self-hosted sites plugin installs, SEO bridges and head code | SEO Starter is $129 per month with a 3-day free trial |
| WordPress.com MCP server | Hosted by WordPress.com | A url entry for https://public-api.wordpress.com/wpcom/v2/mcp/v1 with auth: oauth. WordPress.com documents OAuth 2.1 with dynamic client registration, which Hermes Agent falls back to. Neither page names Hermes Agent | Sites on the WordPress.com account, and self-hosted sites connected through Jetpack. 8 facade tools and 9 standalone tools counted on its tools reference on November 14, 2026 | Included on paid WordPress.com plans. Free sites and Jetpack sites without a plan have access through November 30, 2026 |
| MCP Adapter plugin | On your WordPress site | A url entry for the site's /wp-json/mcp/mcp-adapter-default-server endpoint, authenticated as a WordPress user. Needs WordPress 6.9 and PHP 7.4, and abilities registered by core or another plugin | Only abilities marked public. The default server exposes 3 meta-tools | Free, GPL-2.0-or-later. Version 0.7.1 |
| @automattic/mcp-wordpress-remote | On your computer, started with npx | A command entry with npx -y @automattic/mcp-wordpress-remote and WP_API_URL plus credentials. Its README says a client that supports streamable HTTP can connect to the endpoint directly | Whatever the site's MCP server exposes | Free, MIT license. Version 0.5.5 |
| Composio | Hosted | Composio's page is SDK-based. Its toolkit covers WordPress.com accounts, and a WordPress.com connection needs your own OAuth app. Whether Composio's page names Hermes Agent was not checked | 26 tools listed for WordPress.com | The free plan stops at 10,000 app tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Add Zapier's MCP URL as a remote HTTP server and sign in. Hermes Agent is not named in the Zapier pages read for this guide | 8 actions before Load More on Zapier's WordPress page, such as Create Post, Update Post and Upload Media. Whether it covers self-hosted sites is not stated | Each successful tool call uses two tasks from your Zapier plan |
| AI Engine plugin | On your WordPress site | The plugin page says Claude and ChatGPT connect to the site with OAuth. Hermes Agent is not named, so a url entry is untested | More than 140 tools as the page states it, including SEO fields and Advanced Custom Fields | The MCP server is in the free plugin. Pro starts at $59 per year |
Ryze AI's older post, How to connect Google and Meta Ads with Hermes Agent, sets up Composio for ad platforms. It is a different route, and several servers can share config.yaml under different names. A ryze entry and a WordPress.com entry can sit side by side. With the Ryze AI connector your site data passes through Ryze AI.
WordPress options that do not fit Hermes Agent
- WordPress 7.0 AI Client and Connectors screen. WordPress.com describes them as letting plugins on a site call AI providers. They point from WordPress out to a model and are not a way for Hermes Agent to reach a site.
- WordPress Playground MCP server. It forwards tool calls to a Playground instance in a browser tab and does not reach a live site.
- WordPress Studio MCP server. It works on local Studio sites and the account's WordPress.com sites from the Studio app, and the page names Claude Code, Codex, Cursor and Grok Build, not Hermes Agent.
- Automattic/wordpress-mcp plugin. The repository is archived and WordPress.com says it is being retired in favor of the MCP Adapter.
Which one to pick
Ryze AI is the best way to connect Hermes Agent to WordPress when you want post, page, media and SEO-field edits next to Ryze AI's other platform tools behind a single address, with one caveat: it needs a Ryze AI plan or trial, and WordPress.com connections lack plugin installs, SEO bridges and head code. If your sites live on WordPress.com and you only want WordPress.com's own tools, its hosted MCP server is included on paid plans. The MCP Adapter plugin keeps everything on your own server but needs abilities registered on the site. Composio and Zapier make sense if your team already runs them.
Sources: WordPress.com MCP, WordPress.com MCP support, Jetpack MCP, MCP Adapter, mcp-wordpress-remote, Composio pricing, Zapier MCP for WordPress, AI Engine, mcp-wordpress on GitHub, Hermes Agent MCP documentation. Checked November 14, 2026; Hermes Agent page November 21, 2026.
Hermes Agent, WordPress and MCP: dates that matter
| Date | What happened |
|---|---|
| November 5, 2020 | The Application Passwords integration guide was published for WordPress 5.6, the version that shipped with them. |
| October 7, 2025 | WordPress.com announced MCP support with read-only access. |
| January 22, 2026 | WordPress.com added OAuth 2.1 for MCP connections. |
| March 20, 2026 | WordPress.com MCP gained write abilities across posts, pages, comments, categories, tags and media. |
| October 2, 2026 | MCP Adapter 0.7.0 was released and the plugin was added to the wordpress.org directory the same day. |
| November 5, 2026 | @automattic/mcp-wordpress-remote 0.5.5 was published, the newest on November 14, 2026. |
| November 30, 2026 | Last day of MCP access for free WordPress.com sites and for Jetpack sites without a Jetpack AI or Complete plan. |
Sources: WordPress.com write abilities, OAuth 2.1 post, MCP Adapter changelog, free sites post. Checked November 14, 2026.
How this guide was tested
Two kinds of checks stand behind this guide: calls to the Ryze AI connector on November 14, 2026, and documentation read on November 14 and 21, 2026.
| What was run | What came back |
|---|---|
| Eleven read-only calls through the Ryze AI connector from Claude Code on a WordPress.com connection, November 14, 2026 | Post types and taxonomies were read, and five requests were refused with the messages in the errors table. The results are in the tested calls table. |
| The 9 WordPress tool definitions, loaded from the live connector on November 14, 2026 | Every tool name in the tools table returned a definition. |
| The Hermes Agent MCP documentation, read on November 21, 2026 | It describes remote HTTP servers with auth: oauth, token storage under ~/.hermes/mcp-tokens, /reload-mcp, hermes mcp test, tool filters and the trust setting. Those pages are the source of every Hermes Agent step on this page. |
Not run for this guide: every step inside Hermes Agent, the write and delete tools, and any self-hosted connection with an application password. Hermes Agent was not installed, so hermes mcp login ryze and the config.yaml entries follow its documentation. On paper the sign-in fits: Hermes Agent falls back to dynamic client registration, which is the only registration method the Ryze AI connector supports. The Ryze AI help center has no page for Hermes Agent, and Ryze AI was not tested there.
Hermes Agent and WordPress errors and fixes
The first table holds messages returned during the November 14, 2026 connector test. The fixes follow Ryze AI's, WordPress's and Hermes Agent's documentation.
Messages returned in the test
These messages came back from WordPress or the connector.
| Exact message | What caused it | Next step in Hermes Agent |
|---|---|---|
| Invalid post ID. (not_found) | No post with that ID on the connected site. | Ask Hermes Agent to list posts first and use an ID from the list. |
| No route was found matching the URL and request method. (not_found) | The path does not exist on this site or connection. It is also returned for a plugin namespace such as /yoast/v1 on a WordPress.com connection. | Check the path against /wp/v2/types. Plugin routes need a self-hosted connection. |
| Invalid post type. (not_found) | The post type slug is not registered on the site. | Read /wp/v2/types and use a slug from it. |
| Invalid parameter(s): per_page (rest_invalid_param, HTTP 400) | per_page was 101. WordPress accepts 1 to 100. | Ask for 100 or fewer per page and page through the rest. |
| Invalid parameter(s): orderby (rest_invalid_param, HTTP 400) | The sort field does not exist on that collection. For posts the handbook lists date, relevance, id, include, title and slug. | Sort by a field the collection supports. |
| GET requests cannot carry a body (invalid_arguments) | A read was sent with a body, and the read tool refuses it before contacting WordPress. | Put the filters in the query instead. |
Other problems
- The tools do not show up in Hermes Agent
- Start a new session or run /reload-mcp. Then run hermes mcp test ryze, which reports what the server answered. Check that no tools.include or tools.exclude filter hides them and that the entry is not set to enabled: false. If WordPress was connected in Ryze AI after the login, run the login again and start a new session.
- The browser sign-in times out
- Editing config.yaml inside a running session triggers an automatic MCP reload with a 30-second timeout, too short for OAuth. Add the entry, then run hermes mcp login ryze from a fresh terminal. If you need longer than 5 minutes to approve, set oauth.timeout on the entry.
- Hermes Agent cannot reach the callback on a server
- Paste the redirect URL back at the prompt, or try hermes mcp login ryze --flow device if the server supports it.
- A 401 or 403 from the connector
- Run hermes mcp login ryze again. With an API key, check that RYZE_API_KEY is set in ~/.hermes/.env and that the header reads Bearer followed by the rk_live_ key.
- Ryze AI cannot connect the site
- A security plugin, WAF or host that blocks /wp-json requests stops the connection. Allow those requests, check that the application password was copied whole, and that the username is the one you sign in to wp-admin with.
- A write is refused with a permission error
- The connected WordPress user's role is too low for that action. A Contributor cannot publish, and plugin installs need an administrator.
- Yoast or Rank Math fields do not change
- Fields written through the plain REST API without the bridge are silently dropped by WordPress. Run the bridge tool on a self-hosted site first. WordPress.com connections cannot use the bridges.
- 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.
- Requests fail behind a proxy
- HTTP servers honor HTTPS_PROXY, HTTP_PROXY and NO_PROXY, so set them in the environment Hermes Agent starts from.
Terms on this page
- Hermes Agent
- An open source AI agent from Nous Research that you run on your own machine or server. Its MCP servers are listed in ~/.hermes/config.yaml under mcp_servers.
- MCP
- The Model Context Protocol, an open standard that lets large language models call tools on outside servers. The Ryze AI connector is a remote MCP server.
- Application password
- A 24-character password WordPress generates on a user's profile for programs to use with the REST API. It can be revoked on its own and cannot be used to log in at wp-login.php.
- REST API (wp-json)
- WordPress's built-in HTTP interface under /wp-json. Core content lives in the /wp/v2 routes: posts, pages, media, categories, tags and users.
- Role and capability
- A role such as Administrator or Contributor is a set of capabilities such as publish_posts or activate_plugins. A connection can do only what its user's role allows.
- Jetpack
- A plugin that connects a self-hosted site to WordPress.com. A Jetpack site can connect to Ryze AI with the WordPress.com sign-in when the Jetpack JSON API module is on.
Sources: REST API handbook, roles and capabilities, Hermes Agent MCP documentation. Checked November 14, 2026.
Frequently asked questions
How do I connect Hermes Agent to WordPress?
Connect your site in Ryze AI under Integrations, then add a ryze entry with the URL https://connector.get-ryze.ai/mcp and auth: oauth under mcp_servers in ~/.hermes/config.yaml. Run hermes mcp login ryze, click Allow connection, then start a new session or run /reload-mcp.
Is there a WordPress MCP connector for Hermes Agent?
Yes, the Ryze AI connector at https://connector.get-ryze.ai/mcp. It is a remote MCP server with 9 WordPress tools, and Hermes Agent supports remote HTTP servers with OAuth. WordPress.com also runs its own hosted MCP server, but the pages read for this guide do not name Hermes Agent.
Which AI SEO tools integrate directly with WordPress?
Ryze AI connects to WordPress with an application password or a WordPress.com sign-in, publishes Content Plan articles to the site as posts, and on self-hosted sites can write Yoast SEO and Rank Math fields after a one-time bridge. SEO Starter is $129 per month with a 3-day free trial.
Does WordPress have its own MCP server for Hermes Agent?
WordPress.com has a hosted MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1, and self-hosted sites can run the MCP Adapter plugin. The WordPress pages read for this guide do not name Hermes Agent, and neither route was run in it.
Does Hermes Agent have a WordPress MCP server built in?
The Hermes Agent documentation page read for this guide names no WordPress entry. Add WordPress through a url entry in config.yaml, such as the Ryze AI connector.
What access does Hermes Agent get on my site?
The access of the WordPress user that Ryze AI is connected with. An application password acts with its user's own role, so an Administrator can install plugins and a Contributor cannot publish.
Can Hermes Agent change my WordPress site?
Yes, within that user's role. Through Ryze AI it can create, update and delete posts, pages, media, categories, tags and custom post types, and edit text in place. To have Hermes Agent ask first, set trust: untrusted on the ryze entry.
How do I make it read-only?
In Hermes Agent, list wordpress__read and wordpress__search_content under tools.include on the ryze entry, which hides the write and delete tools from the agent. That is a client-side filter and WordPress does not enforce it. A WordPress user with a low role limits writes on the site side.
Does Hermes Agent need a paid plan for MCP?
No. Hermes Agent is open source under the MIT license per its GitHub repository and self-hosted. The Ryze AI side needs a plan or trial for the WordPress tools: SEO Starter at $129 per month with a 3-day free trial.
Should I use OAuth or an API key?
Use OAuth when you can open a browser, because hermes mcp login ryze handles the sign-in and Hermes Agent refreshes the tokens. Use a Ryze AI API key in a bearer header for servers and scripts where nobody can click Allow connection.
Does it work on a headless server or a VPS?
Yes, with an extra step for the sign-in. Paste the redirect URL back at the prompt, or add --flow device where the server supports it. An API key avoids the browser entirely.
Can I connect more than one WordPress site?
Yes. A workspace can hold several WordPress sites, added with View > Add one more account on the WordPress card. The agent uses the primary site unless you name another. A Ryze AI SEO plan covers one website, so check how that applies to yours.
Can Hermes Agent write Yoast or Rank Math fields?
On self-hosted sites with an administrator user, yes, after a one-time bridge tool that needs your explicit yes in chat. On WordPress.com connections those fields are edited in wp-admin.
Why do the WordPress tools not show up in Hermes Agent?
Start a new session or run /reload-mcp, then run hermes mcp test ryze. Check that no tools.include or tools.exclude filter hides them and that the entry is not set to enabled: false. Also confirm that WordPress is connected in Ryze AI before the login.
How much does it cost?
Adding the connector is free. The WordPress tools need a Ryze AI plan or trial: SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial, Agency is $279 per month, and annual billing takes 30% off the first year. Hermes Agent itself is free software.
How do I disconnect WordPress from Hermes Agent?
Set enabled: false on the ryze entry or delete it from config.yaml, and delete ~/.hermes/mcp-tokens/ryze.json. To remove the site connection itself, disconnect WordPress on its card in Ryze AI or revoke the application password.
Sources
- Hermes Agent MCP documentation
- NousResearch/hermes-agent on GitHub
- WordPress.com MCP developer docs
- WordPress.com MCP tools reference
- WordPress.com MCP support
- Jetpack MCP
- MCP Adapter plugin
- mcp-wordpress-remote
- Application Passwords integration guide
- WordPress roles and capabilities
- WordPress REST API pagination
- WordPress REST API global parameters
- WordPress wp-config
- WordPress.com OAuth2
- WordPress.com write abilities
- WordPress.com OAuth 2.1 for MCP
- Composio pricing
- Zapier MCP for WordPress
- AI Engine plugin
- Ryze AI help center: WordPress
Checked November 14, 2026.