Grok + WordPress: connect grok.com or Grok Build to your site

Three products carry the Grok name

They do not share a connector list, so pick the one you use. Grok Build and grok.com both connect today; the Grok Bot app does not yet.

grok.com: your site as a custom connector, in four steps

The custom connector on grok.com has a Name and a Server URL, and no field for a key. So the way in is a sign-in: your site asks Grok to sign in through respira.press, and you approve it there. Once approved, Grok keeps its own token and refreshes it; nothing is copied by hand. This needs Respira 9.1.19 or newer on the WordPress site. An older version lets Grok connect with no sign-in, shows the tools, and then every call fails.

1. Update Respira on the site to 9.1.19 or newer.

   In wp-admin, under Plugins. The version is shown in the Respira for WordPress row.

2. Copy your site's link.

   Open the Respira setup page and choose Grok, or build it yourself: your site's address followed by /wp-json/respira/v1/mcp.

   https://yoursite.com/wp-json/respira/v1/mcp

   Open dashboard setup
3. Add the connector.

   Go to grok.com/connectors, choose New Connector, then Custom. Type a Name (Respira works), paste the link into Server URL, and choose Add Connector.

4. Sign in to Respira and approve.

   The Respira sign-in opens in a new window. Sign in with the account that owns the site, then approve. After that, ask Grok to list your WordPress pages. Real page titles mean it is working.

If Grok says connected and no sign-in opened. The connector was added while the site was on an older version. Update the site to 9.1.19 or newer, choose Disconnect, and add it again.

What was checked. On 3 October 2026 this was run on a live site: the connector was added with the site link, the Respira sign-in opened, and within ten seconds Grok had registered, taken its token and listed the site's pages. If it does not work for you, write to word@respira.press and say what Grok showed.

Grok Build: what it is

Grok Build is the coding agent from xAI that runs in a terminal. Its documentation is at docs.x.ai/build. It speaks the Model Context Protocol: every server you add becomes a set of tools it can call. Respira is one of those servers, and the site it acts on is your own WordPress install. Every command below was run on a real site with grok 1.0.46: the add command, the doctor check, a read and a write on a duplicate.

Grok Build: one command per site, in four steps

1. Open the Respira setup page and choose Grok Build.

   Pick the WordPress site. The page builds the command below with that site's address and key already in it, so there is nothing to type by hand.

   Open dashboard setup How the MCP server works
2. Run the command in a terminal.

   This is its shape. The address is your site followed by /wp-json/respira/v1/mcp, and the key travels in a header, so there is no sign-in step.

   grok mcp add --transport http respira https://yoursite.com/wp-json/respira/v1/mcp --header "Authorization: Bearer <your site key>"

   Grok Build saves it in ~/.grok/config.toml under [mcp_servers.respira]. Add --scope project to save it in ./.grok/config.toml for one project instead.

3. Check the handshake.

   grok mcp doctor respira

   It reports that the server started, the handshake, and how many tools it found. A green result here means the site answered. It does not yet mean the key works, because a site lists its tools before it asks for a key. The next step is the proof.

4. Run a read.

   grok -p "List my WordPress pages with the respira server" --allow "mcp__respira"

   Real page titles from your site mean the address, the key and the site lined up. The --allow part lets this run call the tools of the server named respira: with no one there to approve a call, Grok Build stops before making it. If the answer is No API key found, the header did not reach the site: run the add command again with the key from the dashboard.

Grok Build: a first edit that cannot hurt

This is the write that was tested: copy a page, change one heading on the copy, read it back. The original page is never touched, and the copy is a draft until a person approves it in wp-admin.

On the respira server, duplicate the page titled "About". On that duplicate only, find the first heading and set its text to "Hello from Grok Build". Read the duplicate back and give me its preview link. Do not edit the original page.

On the test site Grok Build duplicated a draft page, changed the first heading on the duplicate, and returned a preview link. A separate read confirmed the new heading on the duplicate and the old one on the original.

A copy first

An edit to a published page lands on a duplicate. A person approves it before it goes live.

A snapshot before each write

Page and element writes save the previous state, and it can be restored for 90 days.

The builder's own format

Respira writes Elementor as Elementor and Bricks as Bricks, so the page stays editable in its builder.

Grok Build: more than one site

Each WordPress site has its own address, so each one is its own command with its own name: respira-shop, respira-blog. The dashboard names them for you. In a prompt, say which server you mean.

Grok Build: the plugin, for all your sites at once

The command above connects one site. The Respira plugin for Grok Build starts the Respira server on your own computer instead, with every site in your Respira setup, so there is no command per site.

1. Set up your sites once.

   This writes your site list to ~/.respira/config.json. Skip it if you already use Respira with another app on this computer.

   npx @respira/wordpress-mcp-server --setup

2. Install the plugin.

   grok plugin install respira-press/respira-wordpress-mcp

   Grok Build asks you to confirm before it installs. The plugin is two small files: a manifest and one server definition. Its README lists every address the server contacts and the one key it needs.

3. Check it started.

   grok mcp doctor

   Look for respira-wordpress in the report, with a handshake and a tool count.

Checked on 2 October 2026 with grok 1.0.46: the plugin installed and the server started with its tool list. The read and the write on this page were run with the one-site command, not through the plugin. Respira was submitted to the Grok Build plugin marketplace the same day; until it is listed there, the command above installs it straight from its repository.

Grok Bot: pending

The Grok Bot app adds connectors from a marketplace, and there is no place to enter a server address. Respira was submitted to xAI's plugin marketplace on 2 October 2026 as respira-for-wordpress; the submission is public and waits for xAI's review: xai-org/plugin-marketplace, pull request #1096.

Once it is listed, Grok Build installs it by name, and this section changes to the steps for Grok Bot. Until then, Grok Bot is the one Grok that does not connect.