By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Grok to WordPress is the Ryze AI connector. Connect the site in Ryze AI with an application password (self-hosted) or a WordPress.com sign-in, then open grok.com/connectors, choose New Connector and Custom, paste https://connector.get-ryze.ai/mcp and sign in to Ryze AI when Grok asks. Grok then has 9 WordPress tools for that site.
- WordPress admin: create an application password under Users, Profile (self-hosted sites)
- Ryze AI: Integrations, Connect on the WordPress card, then enter the site URL, username and password or sign in on WordPress.com
- grok.com/connectors: New Connector, Custom, paste the connector URL
- Ryze AI page: sign in, pick the workspace, press Allow connection, then open a Grok chat
Grok to WordPress at a glance
| Fact | Detail |
|---|---|
| Main way to connect | Ryze AI's hosted MCP connector, which Grok takes by URL as a custom connector |
| Address to paste | https://connector.get-ryze.ai/mcp, the same for every account |
| How Grok signs in | After the URL, Grok asks you to finish authentication. You sign in on the Ryze AI page and press Allow connection |
| WordPress tools in Grok | 9 in total: 2 read (wordpress__read, wordpress__search_content), 6 write, 1 delete (wordpress__delete). 4 of them work only on a self-hosted site |
| Can Grok change the site | Yes, through the write and delete tools, within the role of the connected WordPress user. xAI describes no confirmation step on grok.com; Grok Bot shows an approval card when Auto Review wants your OK, and Grok Build asks first by default |
| Other data in the same Grok chat | Tools for the other platforms connected in the same Ryze AI workspace come from the same address |
| Grok plan | xAI makes connectors available to all Grok users. On The X Subscription, Grok Bot comes with Premium, Super and Ultra, and Plus and Free leave it out |
| Ryze AI price | Free to add. The WordPress tools run on an active plan or trial, and SEO Starter is $129 per month with a 3-day free trial |
| WordPress's own option for Grok | The WordPress.com MCP server from Automattic. Its pages name other assistants and do not name Grok, and it was not tested with Grok |
| WordPress access of the connection | A self-hosted application password acts with its user's role. A WordPress.com or Jetpack connection signs in on WordPress.com and reaches only the core /wp/v2 routes |
| Last tested | Connector checked November 14, 2026 on a WordPress.com connection, with reads sent from Claude Code. No step was run inside Grok |
Before you start
- A Grok account, Grok Bot or Grok Build. xAI says connectors are available to all Grok users, and its connectors page names no separate plan for custom MCP servers. On Grok Business and Enterprise an admin has to add the connector in console.x.ai before members can use it. Grok Bot is its own app that signs in with a Cursor account; Premium, Super and Ultra on The X Subscription include it, while Plus and Free do not.
- A WordPress login that Ryze AI can use. For a self-hosted site, that is the site URL over https, the username you use for wp-admin and an application password. WordPress has shipped application passwords since version 5.6, and they are on by default for every user on a site served over HTTPS. For a WordPress.com or Jetpack site you sign in on WordPress.com, and a Jetpack site needs the Jetpack JSON API module on. Plugin installs, the Yoast and Rank Math bridges and head code also need an administrator.
- An active Ryze AI plan or trial. Adding the connector is free, yet the 9 WordPress tools answer only on a plan or trial. SEO Starter is $129 per month with a 3-day free trial and publishes Content Plan articles to the site. Agency is $279 per month. Paying yearly takes 30% off the first year.
How to connect Grok to WordPress on grok.com
Steps 1 and 2 take place in WordPress and Ryze AI, steps 3 to 5 in Grok. Every account pastes the same address.
Create an application password in WordPress
On a self-hosted site, open Users, then Profile in wp-admin and scroll to Application Passwords. Enter a name such as Ryze AI, press Add New Application Password and copy the result, which is shown once. On a WordPress.com or Jetpack site skip this step and use the sign-in in step 2.
Connect the site in Ryze AI
Sign in to Ryze AI, open Integrations and press Connect on the WordPress card. On the Self-hosted site tab enter the Site URL, your wp-admin username and the application password, then press Continue. On the WordPress.com / Jetpack tab sign in on WordPress.com, approve access and pick the site if the account has several.
Add a custom connector on grok.com
Open grok.com/connectors, press New Connector and pick Custom. Paste https://connector.get-ryze.ai/mcp as the server URL. xAI accepts only servers its own systems can reach over the public internet, and this address is one of them.
Sign in to Ryze AI and allow the workspace
Grok then asks you to complete authentication. On the Ryze AI page, sign in, select the workspace that holds the WordPress connection and press Allow connection.
Ask Grok about the site
xAI says Grok discovers the tools a new connector offers and makes them available in conversations. Open a chat and try: List my 10 most recent WordPress posts with the title, status and date of each.
On authentication, xAI's connectors page says no more than to complete whatever is required once the URL is in. A second xAI page, on tunneling, says OAuth or API key flows for a custom server run inside Grok. No xAI page mentions dynamic client registration. The sign-in and Allow connection screens belong to Ryze AI, as the Ryze AI help center Grok page shows them, and they were not run on grok.com for this guide. The WordPress side is described in the Ryze AI WordPress guide. If the WordPress tools are missing because you connected the site after adding the connector, delete the connector in Grok, add it again and start a fresh chat.
Grok Business, Grok Bot and Grok Build
Three more places take the same address. The WordPress login lives in Ryze AI, so none of them asks for the application password again.
Grok Business and Enterprise (admin)
Team plans put one step at the front: an admin registers the connector in xAI's console. xAI ties adding and removing connectors to Team Read-Write permissions, which admins usually hold.
- Log in at console.x.ai, choose the team, then open Grok Business and Connectors. One xAI page calls the same menu Grok Enterprise.
- Press + Add Connector, choose Other and paste https://connector.get-ryze.ai/mcp.
- Finish whatever authentication the console asks for.
- xAI's page tells members to link their own accounts at grok.com/connectors after a catalog connector is added. The custom server steps stop at authentication, so confirm with your admin how members reach it.
Grok Bot
Grok Bot is a desktop and phone app of its own, apart from grok.com, and it signs in with a Cursor account. According to the Ryze AI help center, Ryze AI is one of the built-in apps on Grok Bot's Connect apps screen. Ryze AI appears nowhere in xAI's documentation, and nobody checked that screen for this guide, so these steps come from the Ryze AI help center.
- Open Connect apps in the Grok Bot sidebar. In the phone app, tap your avatar in the top left corner and choose Connect apps.
- In the box labeled Search across apps and skills, enter Ryze AI. Open the entry whose developer line reads Ryze AI and press Add.
- A browser tab opens on Ryze AI. Sign in, pick the workspaces and press Allow connection.
- Once Authorization complete shows, press Open Grok Bot or Return to Grok Bot.
- Start a new chat. Typing @ lets you attach the app to the task.
No Ryze AI result in the search? The desktop app has a manual route at the foot of Connect apps, Add a custom connector. Give it a name, pick Remote HTTPS as the Type, put the connector URL in Server URL and press Add plugin. xAI also lets you ask a Bot to add the URL. An app you connect belongs to your account, so every Bot you run can use the WordPress site. If an older hand-added copy of Ryze AI is still installed, the Ryze AI help center says to uninstall it to avoid a double set of tools.
Grok Build CLI
Grok Build, xAI's coding agent for the terminal, registers a remote server with one command.
- Run the command below in a terminal.
- On first use of the server, a browser opens for the Ryze AI sign-in. Finish it there.
- In the terminal interface, /mcps (alias /connectors) opens the MCP tab. Select the ryze server and press i to authenticate it.
grok mcp add --transport http ryze https://connector.get-ryze.ai/mcpGrok Build stores the OAuth tokens in ~/.grok/mcp_credentials.json and namespaces tools as <server>__<tool>, so the WordPress tools sit under the ryze server name. When no browser can open the sign-in page, /mcps shows its URL in a panel you can copy, a change from release V1.0.74.
Grok and MCP: the facts in one table
xAI (its documentation now names the company SpaceXSI) runs three products that take MCP servers, each with its own rules. Read across a row to compare them.
| Question | grok.com and team admins | Grok Bot | Grok Build |
|---|---|---|---|
| Where the address goes | New Connector, then Custom, at grok.com/connectors. On team plans an admin first uses + Add Connector, then Other, in the console | The Connect apps screen; for a server outside the catalog, the desktop form or a Bot asked to add it | The command grok mcp add, or a server table written into config.toml under ~/.grok |
| Transports | A public URL. Grok turns down localhost and private network addresses. xAI's tunneling notes mention SSE and Streamable HTTP servers | Remote HTTPS by URL. Command servers start on the cloud machine the Bot works on | HTTP by URL (the settings reference says HTTP/SSE), or stdio for a command on your machine |
| Sign-in | Whatever authentication the server needs, finished in Grok | Provider login in a browser tab, to be done in roughly 10 minutes. Cursor's connector backend keeps the tokens | Browser login on first use, with tokens saved in mcp_credentials.json under ~/.grok |
| Approval before a call | xAI describes none; tools are used when a question touches the service | Auto Review is on from the start and shows a card (Allow once, Always allow, Deny) for actions it wants you to OK | Ask is the starting mode. Allow and deny rules can name MCP tools through the MCPTool filter, and deny wins |
| Plan | Connectors are open to all Grok users | Premium, Super or Ultra on The X Subscription, not Plus or Free | The MCP page names no plan |
| Managing a server later | Back on grok.com/connectors. If a server address changes, delete the old connector and create a new one | Click the connected count next to the Connect apps heading. Each app has Reconnect and Remove, and its tools can be turned off one by one | /mcps: Space switches a server on or off, x deletes it. From the shell, grok mcp remove |
Sources: xAI's Grok connectors, custom MCP tunneling, connector management, Grok Bot apps, Grok Bot approvals, Grok Bot plans, Grok Build MCP servers and Grok Build permissions, checked November 14, 2026. Ryze AI steps: the Ryze AI help center Grok page.
WordPress access and roles
Grok never sees the application password or the WordPress.com sign-in. Ryze AI keeps the connection, and three choices there decide what Grok can touch.
- Self-hosted site with an application password
- You enter the Site URL, your wp-admin username and the password. WordPress acts on every request as that user, so the user's role sets the limit. The password can be viewed and revoked on the same profile page and cannot be used to log in at wp-login.php.
- WordPress.com or Jetpack site
- You sign in on WordPress.com and approve access. Ryze AI documents the core /wp/v2 routes for this connection type, and no plugin routes. Plugin installs, the Yoast and Rank Math bridges and head code do not work on it.
- Which site Grok works on
- One workspace can hold several WordPress sites. The primary site is used unless you name another in the chat, and the live tools accept a connection_id to aim at one site.
A self-hosted connection has no app scopes of the kind Shopify or Google use: the application password carries its user's own access. The table lists what Ryze AI documents for each connection type.
| Area | Access |
|---|---|
| Posts, pages, media, categories, tags and custom post types | Read, create, update and delete through the REST API, on both connection types, as far as the WordPress user's role allows |
| Targeted text edits | Find text in a post's raw content and replace it without resending the whole post, on both connection types |
| Yoast SEO and Rank Math fields | Self-hosted only, after a one-time bridge that needs an administrator. On WordPress.com these fields are edited in wp-admin |
| Head code (tracking pixels, verification tags) | Self-hosted only, through a Code Snippets plugin snippet, with an administrator |
| Plugin installs | Self-hosted only, from the wordpress.org directory, with an administrator. Zip files and URLs are not accepted |
| Plugin routes such as /yoast/v1 | Self-hosted connections only. WordPress.com connections reach the core /wp/v2 routes |
Roles and what they mean for Grok
Both connection types end at the role of a WordPress user, so the role table is the closest thing to a scope list. WordPress's role documentation, last updated September 2, 2026, describes the five default roles like this. Ryze AI's tool descriptions treat a 403 answer as a role that is too low.
| Role | What WordPress says it can do | What it means for Grok through Ryze AI |
|---|---|---|
| Administrator | All administration features within a single site, including activate_plugins | Everything the 9 tools offer, including plugin installs, the SEO bridges and head code on a self-hosted site |
| Editor | Publish and manage posts, including other users' posts | Content reads and edits across the site. Not the administrator-only tools |
| Author | Publish and manage their own posts | Content work limited to their own posts |
| Contributor | Write and manage their own posts but not publish them | Drafting only. Publishing is outside the role |
| Subscriber | Manage their own profile, with the read capability only | Too low for editing. Expect 403 answers |
Not covered by any role: robots.txt on WordPress is outside what the tools change, and Ryze AI's Technical Audit gives step-by-step instructions instead. Elementor page text is reachable only where the post type exposes meta._elementor_data. Yoast and Rank Math fields sent through the plain REST API without the bridge are silently dropped by WordPress. A security plugin, WAF or host that blocks /wp-json requests stops the connection until those requests are allowlisted. Which WordPress.com scope the Ryze AI sign-in requests is not documented, so this page does not name one.
Sources: WordPress's roles and capabilities, REST API authentication, application passwords guide, WordPress.com OAuth2 and Jetpack JSON API, checked November 14, 2026. Connection types: the Ryze AI WordPress guide.
Removing access
To take the site away from Grok, remove the connector: delete it at grok.com/connectors, or have the team admin delete it in the console. Grok Bot users press Remove on the app; Grok Build users type grok mcp remove ryze. Ending Ryze AI's own access takes one more step: disconnect the site on its WordPress card, and on a self-hosted site revoke the application password under Users, Profile in wp-admin.
What Grok can do in WordPress
Through Ryze AI, Grok gets 9 WordPress tools: 2 that read, 6 that write and 1 that deletes. Every call runs as the connected WordPress user. Writes and deletes are separate tools, so the approval settings of a client can treat them differently.
| 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__installPlugin | Write | Installs and activates a plugin from the wordpress.org directory on a connected self-hosted 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 tracking snippets, pixels and verification tags. |
| wordpress__delete | Delete | Runs a DELETE WordPress REST API request, for example to delete a post. |
Whether Grok pauses before a change depends on the product, as the table of Grok facts above shows. xAI describes no approval step on grok.com, so a line such as wait for my yes is an instruction to the model. The Yoast bridge, Rank Math bridge and head code tools default to installIfMissing false, and their descriptions require your explicit yes in chat before the Code Snippets plugin is installed. The chat inside Ryze AI is separate: its Tool approvals picker starts on Skip all approvals, and Approve write & delete or Manual approve make that chat ask first. Scheduled tasks run without an approval step.
WordPress limits
WordPress publishes no request quota for its REST API. Its handbook caps a page of results at 100 records, and the WordPress.com API guidelines ask developers not to make excessive calls without giving a number. That is an absence of a figure on the pages opened, not a statement that no limit exists. Ryze AI adds limits that hold in every client, Grok included: plugin installs take directory plugins only, and a security plugin or host that blocks /wp-json stops the connection.
Limits in numbers
| Limit | Figure | Set by |
|---|---|---|
| Records per request | per_page takes 1 to 100. The posts reference gives a default of 10 | WordPress REST API |
| Totals for paging | Every paginated response carries X-WP-Total and X-WP-TotalPages headers | WordPress REST API |
| Request quota | No figure on the REST API handbook pages or the WordPress.com MCP pages opened | Not stated |
| Application password | 24 characters, letters and digits only; on by default for users on https sites | WordPress |
| Trash | Trashed posts, pages, attachments and comments are deleted for good after 30 days by default (EMPTY_TRASH_DAYS). Deleted media, categories and tags on WordPress.com are permanent | WordPress, WordPress.com |
| Revisions and autosave | Autosave every 60 seconds by default; revisions are on by default and can be capped or switched off | WordPress |
| Size of one tool call | path up to 2,000 characters. edit_content takes 1 to 50 edits per call, old_string up to 20,000 characters and new_string up to 100,000. search_content takes a pattern up to 500 characters and 0 to 10 context lines. addHeadCode takes html up to 8,192 characters | Ryze AI tool definitions, seen November 14, 2026 |
| Grok Bot connector that stops answering | Times out after three minutes, per the release note of August 12, 2026 | xAI |
| Grok Build timeouts | 30 seconds for a server to start, 6,000 seconds per tool call; both are defaults | xAI |
Sources: REST API pagination, posts reference, wp-config settings, WordPress.com API guidelines and application passwords guide, checked November 14, 2026; Grok Bot apps, Grok Bot changelog and Grok Build MCP servers, checked November 14, 2026.
What the connection returned in the test
Nine wordpress__read calls went through the Ryze AI connector on November 14, 2026, on a WordPress.com connection in a test workspace. Claude Code sent them; it uses the same address as Grok. Two succeeded and seven were refused on purpose. No call read posts, pages, media or users, so this table shows what the connection and the REST API answer, not what is on any site.
| Path read | What came back |
|---|---|
| /wp/v2/types | Worked. 18 post types, including post, page, attachment and several types that Jetpack adds |
| /wp/v2/taxonomies | Worked. 6 taxonomies, including category and post_tag |
| /wp/v2/posts/999999999, an ID that does not exist | Refused as not_found with the message Invalid post ID. |
| /wp/v2/no-such-route | Refused as not_found with the message No route was found matching the URL and request method. |
| /wp/v2/types/not_a_type | Refused as not_found with the message Invalid post type. |
| /wp/v2/posts with per_page 101 | Refused with HTTP 400 and the code rest_invalid_param, because the maximum is 100 |
| /wp/v2/posts sorted by a field that does not exist | Refused with HTTP 400 and the code rest_invalid_param for orderby |
| /wp/v2/types sent with a body | Refused by the connector before any request, as invalid_arguments |
| /yoast/v1, a plugin namespace | Refused as not_found, which matches the rule that a WordPress.com connection reaches only /wp/v2 routes |
First 3 prompts to run
Each prompt says what to ask Grok. Answers come from your own site. The tested reads above show only what the connection returned on a test workspace.
1. List recent posts and their status
List my 20 most recent WordPress posts with the title, status, date and category of each, and mark the ones that are still drafts.
Tools used: wordpress__read
What comes back: A table of posts with the four fields and the drafts marked. The site is not changed.
2. Swap one phrase inside a long post
Search the post with ID 123 for the phrase old pricing and show me each matching line with its line number. Leave the text alone until I answer yes and give you the new wording.
Tools used: wordpress__search_content, then wordpress__edit_content once you agree
What comes back: The matching lines with line numbers and context. After your yes, one find-and-replace edit is written and the rest of the post stays as it was.
3. Draft a post, then change its category
Create a draft post titled with the text I give you, using the body I paste. Then show me the post as saved and list my categories so I can pick one.
Tools used: wordpress__write, then wordpress__read
What comes back: A create request through the write tool, then a read of the post and the category list. Nothing is published unless you ask for it.
Replace the post ID and the phrase with your own. On grok.com the yes in prompt 2 is an instruction to Grok, since xAI describes no approval step there, so keep it in every prompt that edits or deletes. The prompts change data, so this page shows no result for them.
10 jobs to hand to Grok
Ten jobs to give Grok, each with the Ryze AI tool behind it. The last four need a self-hosted connection with an administrator. None of the jobs was run for this page: the reads that ran are in the table of tested reads, and the tools that change a site were not called.
| Job | What to ask Grok | Tool | On the default connection |
|---|---|---|---|
| Recent posts | List recent posts with title, status, date and category. | wordpress__read | Works on both connection types. Up to 100 items per request |
| Custom post types | Which post types does the site have, and what are the latest items of each custom type? | wordpress__read | Works on both. The /wp/v2/types read was tested |
| Find a phrase | Find every line in a post or page that contains a phrase. | wordpress__search_content | Works on both |
| Fix a phrase | Replace a phrase in one post without resending the whole post. | wordpress__edit_content | Works on both, if the role may edit that post |
| Draft a post or page | Create a draft post or page from text I give you. | wordpress__write | Works on both |
| Titles, excerpts and terms | Change a post's title, excerpt, status, categories or tags. | wordpress__write | Works on both |
| Image alt text | Update alt text and captions in the media library. | wordpress__write | Works on both. Media is among the resources the tools cover |
| Delete a post or page | Delete a post or page I name. | wordpress__delete | Works on both, if the role allows it. Set approval for this tool where the client offers it |
| Yoast or Rank Math fields | Write the SEO title, meta description and focus keyword for these posts. | wordpress__enableYoastRestBridge or wordpress__enableRankMathRestBridge, then wordpress__write | No. Self-hosted with an administrator only, after a one-time bridge you approve |
| Tracking or verification tag | Add this verification tag to the head of every page. | wordpress__addHeadCode | No. Self-hosted with an administrator only |
7 ways to connect Grok to WordPress
Seven ways to give Grok access to WordPress are worth knowing. The Ryze AI connector is this guide's main way, because one public address goes into grok.com, Grok Bot and Grok Build, the site is connected once in Ryze AI and nothing has to run on your computer. WordPress.com's own server is the closest alternative, and it is hosted too. None of the WordPress.com pages names Grok, and only Zapier's client list and the WordPress Studio page do. Four more options that do not fit follow the table.
| Way | Runs where | How to add it in Grok | What it reaches | Cost |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every account | A custom connector with https://connector.get-ryze.ai/mcp at grok.com/connectors, after an admin adds it on team plans. Grok Bot: Connect apps per the Ryze AI help center, or a Remote HTTPS custom connector. Grok Build: grok mcp add --transport http. Then the Ryze AI sign-in | Posts, pages, media, categories, tags, users, plugins and custom post types through the REST API, plus content search and targeted edits. On self-hosted sites also the Yoast and Rank Math bridges, head code and directory plugins | Connector free. SEO Starter $129 per month, 3-day free trial; any active plan or trial unlocks the tools |
| WordPress.com MCP server (Automattic) | Hosted by WordPress.com. One connection reaches every site on the account, and Jetpack-connected self-hosted sites use the same server | WordPress.com's pages name other assistants and give no Grok steps. The address is https://public-api.wordpress.com/wpcom/v2/mcp/v1, with OAuth 2.1, PKCE and dynamic client registration. Whether grok.com completes that sign-in was not tested | 8 facade tools and 9 standalone tools, counted on the tools reference on November 14, 2026. The WordPress user role applies. Permanent deletions and DNS changes always ask for confirmation. WooCommerce store data such as prices, stock and orders is not covered | Included on all WordPress.com paid plans. Free sites, and Jetpack sites without a Jetpack AI or Complete plan, have access through November 30, 2026 |
| Zapier MCP | Hosted | Zapier's client list includes Grok. Add Zapier as a connector and sign in; Zapier turns on actions for the apps already connected to your Zapier account. Zapier's per-client page for Grok was not opened | 8 WordPress actions before Load More on Zapier's page: Upload Media, Create Post, Create Tag, Update Post, Create User, Update User, API Request, Find Post. The page does not say whether WordPress.com, self-hosted sites or both are covered | Each successful tool call uses two tasks from your Zapier plan |
| WordPress Studio MCP server | On your computer (the command studio mcp) | Studio's Settings, MCP page has a Connect button next to Grok Build | Local Studio sites: create sites, run WP-CLI commands, take screenshots. The docs also say the agent can work on your WordPress.com sites. They describe no route to a live self-hosted site | No price on the page |
| MCP Adapter plugin (WordPress.org) | On the site. The endpoint is /wp-json/mcp/mcp-adapter-default-server | Grok is not named. xAI documents a static header for Grok Build through --header, and the adapter's own README shows an Authorization header built from an application password for Claude Code. That pairing was not tested | Only abilities that core or another plugin registers and marks public. The default server has 3 meta-tools. The plugin gives no content tools of its own | Free, GPL-2.0-or-later. Version 0.7.1, in the plugin directory since October 2, 2026. Needs WordPress 6.9 and PHP 7.4 |
| AI Engine by Meow Apps (plugin) | On the site, with no relay service | The plugin page names Claude, ChatGPT, Claude Code and OpenClaw, not Grok. No Grok steps | More than 140 tools as the page states it: posts, pages, media, comments, users, taxonomies, menus, SEO fields and more. Pro adds plugins, themes, database and page builders | The MCP server is in the free plugin. Pro starts at $59 per year |
| Open-source servers you run (docdyhr/mcp-wordpress, InstaWP/mcp-wp) | A Node process on your computer | Their READMEs give steps for Claude Desktop and name no Grok. xAI documents local stdio servers for Grok Build only, by command, and says grok.com takes public URLs only | docdyhr/mcp-wordpress states 73 tools and up to 50 sites. InstaWP/mcp-wp gives tool groups and no total | Free. MIT licence for docdyhr, GPL-3.0-or-later for InstaWP |
Four options that do not fit this job
- WordPress Playground MCP server (@wp-playground/mcp). It forwards an agent's calls to a Playground instance running in a browser tab. It works on that instance and not on a live site.
- WordPress Agent Skills. Instruction bundles that teach coding assistants WordPress development patterns. The README table lists 19 skills. They give no access to a site or its data.
- Automattic/wordpress-mcp, the earlier plugin. The repository is archived, and WordPress.com's landing page says it is being retired in favor of the MCP Adapter.
- @automattic/mcp-wordpress-remote. A local stdio-to-HTTP proxy for WordPress MCP servers. Its README says a client that supports streamable HTTP and can authenticate to the site should connect directly. The WordPress 7.0 AI Client and Connectors screen point the other way, from WordPress out to a model, and are not a route for Grok.
Which one to pick
Ryze AI is the best way to connect Grok to WordPress for reading, editing and publishing posts, pages and media from grok.com, Grok Bot or Grok Build, with one caveat: on a WordPress.com connection the plugin installs, SEO plugin bridges and head code do not work, and the tests so far covered reads on a WordPress.com connection only. If you run only WordPress.com sites and want the hosted server Automattic maintains, read WordPress.com's MCP page, which does not name Grok and was not tested with it. Choose WordPress Studio when the target is a local Studio site, and Zapier when your team already runs its WordPress actions there. The self-hosted plugins and open-source servers suit teams that want the server on their own site or machine and can pair them with Grok Build.
Sources: WordPress.com MCP developer page, WordPress.com MCP support, tools reference, MCP Adapter, mcp-wordpress-remote, WordPress Studio MCP, WordPress Playground MCP, WordPress Agent Skills, Zapier WordPress MCP, Zapier MCP quickstart, AI Engine, docdyhr/mcp-wordpress and InstaWP/mcp-wp, checked November 14, 2026; xAI Grok connectors and Grok Build MCP servers, checked November 14, 2026. Ryze AI side: the Ryze AI WordPress guide.
WordPress and Grok: dates that matter
| Date | What happened |
|---|---|
| October 7, 2025 | WordPress.com announced MCP support. Access was read-only at first, and the post said write access would come next. |
| November 14, 2025 | The WordPress developer blog introduced the Abilities API and said its first implementations would ship in WordPress 6.9. |
| January 22, 2026 | WordPress.com added OAuth 2.1 for MCP connections. |
| February 2, 2026 | SpaceX announced that it had acquired xAI. xAI's docs now print the name SpaceXSI. |
| February 5, 2026 | WordPress.com announced its official connector for Claude. |
| March 20, 2026 | WordPress.com MCP gained write tools: 19 new writing abilities across posts, pages, comments, categories, tags and media. |
| May 6, 2026 | Connectors arrived in Grok on the web, iOS and Android. The launch post also brought Bring Your Own MCP, the custom server option. |
| August 11, 2026 | Grok Bot launched as a beta. |
| August 24, 2026 | WordPress.com announced its plugin for ChatGPT. |
| October 2, 2026 | The MCP Adapter reached version 0.7.0 and entered the wordpress.org plugin directory. The same day Grok Bot's Marketplace screen took the name Connect Apps (V0.67.0). |
| October 12, 2026 | The X Subscription began, bundling Grok, Grok Bot, Cursor and X Premium into one plan. |
| November 2, 2026 | Grok Bot 1.0 was announced. Grok Build V1.0.74, out that day, puts an MCP sign-in URL in the /mcps panel when no browser opens. |
| November 3, 2026 | WordPress.com opened MCP access to free sites for a limited time. |
| November 13, 2026 | WordPress.com's MCP developer page and support pages were last updated or reviewed. The Grok Bot page on computer and apps was last changed and now describes the Add a custom connector form. |
| November 30, 2026 | Last day of MCP access for free WordPress.com sites and for Jetpack-connected sites without a Jetpack AI or Complete plan. |
Sources: WordPress.com posts on MCP support, OAuth 2.1, the Claude connector, write tools, the ChatGPT plugin and free-site access, the Abilities API post and the MCP Adapter plugin page, checked November 14, 2026; xAI news on SpaceX, Grok connectors, Grok Build, Grok Bot, The X Subscription and Grok Bot 1.0, and the Grok Bot and Grok Build changelogs, checked November 14, 2026.
How this guide was tested
The connector part of this guide was tested on November 14, 2026, through the Ryze AI connector in a test workspace with one WordPress connection. Claude Code sent the calls; Grok sent none. The response links show that the connection was a WordPress.com site.
| What was run | What came back |
|---|---|
| The tool list from the live connector | All 9 WordPress tool names loaded by name, and each returned a definition. Every tool takes a workspace and an optional connection_id; read, write and delete take a path, a query and a body |
| wordpress__read, 9 calls | Two worked and seven were refused on purpose. The tested reads table has each path and its answer |
| Paging information | Responses carried total and totalPages fields, with 0 on the two schema routes, which are not paginated collections |
| The page size cap | A request for 101 records per page was refused, which confirms the maximum of 100 |
| A plugin route on a WordPress.com connection | Refused as not_found, matching the rule that this connection type reaches only /wp/v2 routes |
| Rate limits and quotas | No rate limit or quota figure appeared in any response |
Nothing was tried inside Grok itself. No connector went into grok.com, the xAI console, Grok Bot or Grok Build, so the Grok steps rest on xAI's pages as they read on November 14, 2026, and the Grok Bot catalog steps on the Ryze AI help center. Claude Code was the stand-in client, on the same connector address. No call was made on a self-hosted connection, so no permission error (401 or 403) was seen, and no bridge, plugin install or head code call was run. No read returned site content, and wordpress__search_content, wordpress__write, wordpress__edit_content and wordpress__delete were not called, because writes change a site. WordPress.com's own server and every other way in the table were not tested.
Errors and fixes
Exact error messages from the test
Each message below is copied from the test of November 14, 2026, except the last, which is described because the original contains a dash. Grok may repeat one of them to you; the other two columns say why it happened and what to try.
| Message | Cause | Next step in Grok |
|---|---|---|
| Invalid post ID. | Status not_found. No post with that ID exists on the connected site. | Ask Grok to list posts first and use an ID from the list. |
| No route was found matching the URL and request method. | Status not_found. The path does not exist on this site or connection. It was also the answer for a plugin namespace (/yoast/v1) on a WordPress.com connection. | Ask Grok to check the path against /wp/v2/types. Plugin routes need a self-hosted connection. |
| Invalid post type. | Status not_found. The post type slug is not registered on the site. | Ask Grok to read /wp/v2/types and use a slug from it. |
| Invalid parameter(s): per_page | HTTP 400, code rest_invalid_param. per_page was 101, and WordPress accepts 1 to 100. | Ask for 100 or fewer per page and go through the rest page by page. |
| Invalid parameter(s): orderby | HTTP 400, code rest_invalid_param. The sort field does not exist. For posts the handbook lists date, relevance, id, include, title and slug. | Ask Grok to sort by a field the collection supports. |
| A message that GET requests cannot carry a body and that filters go in query | Status invalid_arguments. A read was sent with a body, and the read tool refuses it before contacting WordPress. | Ask Grok to put the filters in the query and resend. |
Other problems
- The WordPress tools are missing in Grok
- Connected the site in Ryze AI only after adding the connector? Delete the connector in Grok, create it again and start a fresh chat.
- grok.com will not save the connector
- Grok only takes servers it can reach on the public internet, which the Ryze AI address is, so look for a typo in https://connector.get-ryze.ai/mcp. Team plans need an admin to add it in console.x.ai before anyone else can.
- Ryze AI cannot reach the site
- A security plugin, WAF or host that blocks /wp-json requests stops the connection until those requests are allowlisted. Application passwords need a site served over https.
- A 403 answer on a write
- The connected WordPress user's role is too low for that action. Connect with a user whose role covers it, such as an Editor for content or an Administrator for plugins.
- SEO plugin fields do not stick
- Yoast and Rank Math fields written through the plain REST API without the bridge are silently dropped. On a self-hosted site, ask Grok to enable the bridge first and approve the Code Snippets install when asked. On WordPress.com, edit those fields in wp-admin.
- Plugin install, bridge or head code does not work
- These work only on a self-hosted connection made by an administrator. A WordPress.com connection reaches only the core /wp/v2 routes. Plugin installs can crash a site, so approve each one.
- Elementor text cannot be edited
- Elementor page text is reachable only where the post type exposes meta._elementor_data. Otherwise edit it in wp-admin.
- Grok edits the wrong site
- Several sites can sit in one workspace. The primary site is used unless you name another, so name the site in the prompt.
- Grok Bot shows Ryze AI as Disabled by team admin
- Grok Bot applies the team's Cursor connector policy, and that policy blocks the app. Ask your Cursor team admin to turn it on.
- The same tools appear twice in Grok Bot
- Two copies are installed, the built-in Ryze AI app and an earlier hand-added server. Uninstall the hand-added one.
- The tools say a subscription is required
- Without an active Ryze AI plan or free trial the WordPress tools stay locked. Begin the trial, then ask Grok again.
- Grok Build cannot open the sign-in page
- From V1.0.74 the /mcps panel prints the sign-in URL. Press c to copy it and paste it into a browser.
Terms on this page
- Custom connector
- Grok's name for an MCP server you add yourself by URL, outside its built-in list and its catalog.
- MCP
- The Model Context Protocol, an open standard that lets AI apps call tools on outside systems. grok.com, Grok Bot and Grok Build all accept MCP servers.
- 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 Editor is a set of capabilities such as publish_posts or activate_plugins. A connection can do only what its user's role allows.
- Jetpack connection
- Links a self-hosted site to a WordPress.com account. Its JSON API forwards authenticated REST requests from WordPress.com to the live site.
- Connect apps
- Grok Bot's screen for adding apps and skills. It was called Marketplace until release V0.67.0 of October 2, 2026.
Sources: WordPress's application passwords guide, REST API handbook, roles and capabilities and Jetpack JSON API, checked November 14, 2026; xAI's Grok connectors and the Grok Bot changelog, checked November 14, 2026.
Frequently asked questions
How do I connect Grok to WordPress?
First connect the site in Ryze AI: enter the Site URL, your wp-admin username and an application password, or sign in on WordPress.com. On grok.com/connectors pick New Connector, then Custom, and enter https://connector.get-ryze.ai/mcp. Finish by signing in to Ryze AI, choosing the workspace and pressing Allow connection.
Is there a WordPress MCP server for Grok?
Yes, several. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 9 WordPress tools and goes into Grok as a custom connector. Automattic runs the WordPress.com MCP server, and WordPress.org has the MCP Adapter plugin. Neither WordPress.com's pages nor the adapter's names Grok, and neither was tested with it.
What is the WordPress MCP server URL for Grok?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every account. The WordPress.com MCP server uses https://public-api.wordpress.com/wpcom/v2/mcp/v1. A site running the MCP Adapter plugin has its own endpoint at /wp-json/mcp/mcp-adapter-default-server.
Does WordPress have an official MCP server?
Yes. WordPress.com offers an MCP server built into its platform, launched October 7, 2025 with read-only access and given write tools on March 20, 2026. For self-hosted sites, WordPress.org publishes the MCP Adapter plugin, which turns abilities that the site registers into MCP tools. Neither one names Grok in its documentation.
Can Grok publish posts to WordPress?
Grok can create and update posts and pages through the wordpress__write tool, within the role of the connected WordPress user, and you can ask it to leave a post as a draft. Ryze AI also publishes Content Plan articles to the site as a separate feature on SEO Starter.
Can Grok update image alt text in the WordPress media library?
Yes. Media is one of the resources the write tool covers on both connection types, so you can ask Grok to read the media items and update alt text and captions. The tools that change a site were not run for this page.
Do I need an application password?
For a self-hosted site, yes: you enter the Site URL, your wp-admin username and an application password generated under Users, Profile. For a WordPress.com or Jetpack site you sign in on WordPress.com and need no password.
Which Grok plan do I need?
xAI says connectors, custom MCP connectors included, are available to all Grok users, and that on Grok Business and Enterprise an admin must add the connector in the console first. Grok Bot is included in Premium, Super and Ultra on The X Subscription, and Plus does not include it.
Can Grok edit Yoast or Rank Math fields?
On a self-hosted site, yes, after a one-time bridge. The bridge tools need an administrator and install a Code Snippets plugin snippet only after your explicit yes in chat. On a WordPress.com connection these fields are edited in wp-admin.
Can Grok install WordPress plugins?
On a self-hosted site with an administrator, the wordpress__installPlugin tool installs and activates plugins from the wordpress.org directory. Zip files and URLs are not accepted, and a plugin install can crash a site, so approve each one.
Can I connect more than one WordPress site?
Yes. Several sites can be connected to one workspace with Add one more account, and the primary site is used unless you name another in the chat. Name the site in the prompt when you want the other one.
Does it work with WordPress.com and Jetpack sites?
Yes, with limits. A WordPress.com or Jetpack connection signs in on WordPress.com and reaches only the core /wp/v2 routes. Plugin installs, the SEO bridges and head code need a self-hosted connection. The tests on November 14, 2026 ran on a WordPress.com connection.
How much does it cost to connect Grok 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, Agency is $279 per month, and annual billing takes 30% off the first year.
How do I disconnect WordPress from Grok?
Delete the connector at grok.com/connectors, press Remove on the app in Grok Bot, or run grok mcp remove ryze in Grok Build. To end Ryze AI's access too, disconnect the site on its WordPress card and revoke the application password in wp-admin.
Why do the WordPress tools not show up in Grok?
If you connected the site in Ryze AI after adding the connector, delete the connector in Grok, add it again and start a fresh chat so the tool list refreshes.