MCP serverWhat Grok Build 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.
It is a different product from the Grok chat on grok.com and from the Grok Bot app, even though all three carry the Grok name. This page is about Grok Build only. What was tried with the other two is at the end.
The setup, in four steps
- 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.
- 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.terminal 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.tomlunder[mcp_servers.respira]. Add--scope projectto save it in./.grok/config.tomlfor one project instead. - Check the handshake.
terminal grok mcp doctor respiraIt 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.
- Run a read.
terminal grok -p "List my WordPress pages with the respira server"Real page titles from your site mean the address, the key and the site lined up. 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.
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.
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.com and Grok Bot: what was tried
Both were tried on 1 October 2026, and neither completed a read, so neither has a setup guide here.
grok.com. The custom connector asked for a name and a server address.
It listed Respira's tools, then had no field for a key and did not start a sign-in, so
every call came back with No API key found.
Grok Bot. The app adds connectors from its own marketplace, and there was no place to enter a server address. Respira is not in that marketplace.
This page changes when one of them connects. Until then, Grok Build is the way in.
Questions
Does this work with grok.com or the Grok Bot app?
Not yet. On 1 October 2026 the custom connector on grok.com took a name and a server address and nothing else: it listed the tools, then had no way to send a key and did not start a sign-in. The Grok Bot app installs connectors from its own marketplace only, and Respira is not in it. Grok Build, the terminal agent, is the Grok product that connects today.
Where does the key go?
Into ~/.grok/config.toml on your computer, in plain text, under the server name you chose. Treat that file like a password. Copy the command from the Respira dashboard after choosing the access level you want, and the key in it carries that level and nothing more.
Can Grok Build break my live WordPress site?
Page and element writes take a snapshot first, and an edit to a published page lands on a duplicate. The live page changes when a person approves the duplicate in wp-admin. Every snapshot can be restored for 90 days.
Can I connect more than one WordPress site?
Yes, one command per site. Each WordPress site has its own address, so give each one its own server name, for example respira-shop and respira-blog. Then name the server in your prompt.
Does it work with Elementor, Divi and Bricks?
Yes, plus 14 more. Respira reads and writes each page builder in its own storage format, so a Bricks page stays editable in Bricks. The write on this page was tested on a Bricks page.
