Respira for WordPress welcomes Grok

Grok can now read and edit your WordPress site through Respira for WordPress. It works on grok.com, in Grok Build, and inside Respira AER on your own xAI key.

Grok reads and writes your site in your page builder's own format, across 17 builders, so an Elementor page stays an Elementor page and a Bricks page stays a Bricks page. It gets the same guardrails every other agent gets: an edit to a published page lands on a copy first, every write takes a snapshot, and the live page changes when a person approves.

Don't panic, in other words. Bring a towel if you like.

Three products carry the Grok name

xAI ships Grok in three places, and they do not share a connector list, so each one connects in its own way. grok.com is the chat in your browser. Grok Build is the terminal agent. Grok Bot is the always-on app with its own computer. The first two connect today. The third is waiting for a review.

grok.com: your site as a custom connector

The custom connector on grok.com has a Name and a Server URL, and nowhere to paste a key. So the way in is a sign-in. Your WordPress site asks Grok to sign in through respira.press, you approve it there, and Grok keeps its own token from then on. Nothing is copied by hand.

1. Update Respira for WordPress on the site to 9.1.19 or newer.
2. Copy your site's link. It is your site's address followed by /wp-json/respira/v1/mcp, for example https://yoursite.com/wp-json/respira/v1/mcp. The setup page in your dashboard shows it under Grok.
3. On grok.com/connectors, choose New Connector, then Custom. Give it a name, paste the link into Server URL, and choose Add Connector.
4. The Respira sign-in opens. Sign in with the account that owns the site and approve. Then ask Grok to list your WordPress pages.

I ran those four steps on my own site this morning, from the empty form to Grok reading back the page list. Add one connector per WordPress site.

Grok Build: one command per site

Grok Build reads its servers from ~/.grok/config.toml, and one command adds a WordPress site, with the site key in a header:

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

You do not need to type that yourself. Choose Grok Build on the setup page in your dashboard, pick the site, and the command arrives with that site's address and key already in it. grok mcp doctor respira checks the handshake, and asking Grok Build to list your WordPress pages with the respira server is the real test.

Grok Bot: submitted, waiting for review

Grok Bot installs from xAI's plugin marketplace and has no place to type a server address, so a listing is the only way in. Respira for WordPress is submitted to that marketplace as respira-for-wordpress. The pull request passes its automated checks and waits for xAI's reviewer. When it is merged, the same listing appears in Grok Build's marketplace too.

Respira AER on your xAI key

Respira AER, the chat in your Respira dashboard that works across every site you connected, now takes an xAI key next to Anthropic, OpenAI, Google and OpenRouter. Add it in Respira AER settings. Grok 4.7 is the default, with Grok 4.6, Grok 4.3 and Grok Build 0.1 in the picker, and every run's receipt shows what it cost at xAI's published prices. xAI bills the tokens. Respira adds nothing to them.

One thing to know before you look for the key: the xAI API is billed on its own in the xAI console. A SuperGrok or X Premium plan does not pay for it. The custom connector on grok.com needs no xAI key at all, so if you only want Grok in the chat, start there.

Who did what, afterwards

Connections made this way appear as Grok and Grok Build under Connected apps in your Respira dashboard, apart from your other agents. A site edited from Claude in the morning and Grok in the afternoon reads back as two names, with every change listed under the one that made it.

Where to go next

• Grok and WordPress, with every step, the commands and the questions people ask.
• The setup page in your dashboard, for the grok.com link or the Grok Build command with your site already filled in.
• Respira AER settings, to add an xAI key.