Grok Build + Cuiar
Find the missing labels, then fix them.
- grok mcp add
- ~/.grok/config.toml
- Reads .mcp.json too
Grok Build reads your repo in the terminal. With Cuiar it also reads the running page. It opens staging in a clean QA workspace and takes a snapshot of the accessibility tree.
It finds inputs with no label and images with no alt text, fixes them in src/ and checks the page again, in the same session.
Setup
Add the server to Grok Build.
Grok Build runs on your computer, next to the Cuiar app.
- 1
Install Grok Build
Skip this when it is installed.
curl -fsSL https://x.ai/cli/install.sh | bash - 2
Add the server
grok mcp add --transport http cuiar https://mcp.cuiar.com/mcp - 3
Or write config.toml
Use
.grok/config.tomlwith--scope projectto share it with the team.~/.grok/config.toml [mcp_servers.cuiar] url = "https://mcp.cuiar.com/mcp" - 4
Sign in
The first call opens the cuiar.com sign-in. In the TUI,
/mcpsopens the MCP tab.grok mcp doctor cuiarchecks the server.
Other ways to connect
An API key
For CI and shared machines. Use a key with the
mcpscope.grok mcp add --transport http cuiar https://mcp.cuiar.com/mcp \ --header "Authorization: Bearer ${CUIAR_API_KEY}"Local stdio
Needs the Cuiar CLI, signed in.
grok mcp add cuiar -- cuiar mcpSet up for Claude Code or Cursor already?
Grok Build reads
.mcp.json,.cursor/mcp.jsonand~/.claude.json. A cuiar entry there works with no new step.
Route
The snapshot is the audit.
snapshot returns the accessibility tree with element refs. That is the data an accessibility pass needs, and Grok Build gets it as a tool result next to the code.
- Remote MCPmcp.cuiar.com/mcp
- Best fit
- OAuth on first use, or a key header.
- Local MCPcuiar mcp
- Works
grok mcp add cuiar -- cuiar mcp.- CLIcuiar exec
- Works
- The bash tool runs
cuiar exec --jsonand reads the exit code. - Routineson a schedule
- Works
- Grok Build has no scheduler. Use a Cuiar routine for nightly checks, or
grok -pin CI.
Example tasks
QA passes on staging
01
Run an accessibility pass
“Open staging.example.com in my QA workspace. For home, pricing, sign-up, login, checkout and account, take a snapshot and list inputs with no label, buttons with no name, images with no alt text and skipped heading levels. Fix them in src/ and check again.”
02
Buy in the payment sandbox
cuiar run --workspace qa-checkout --folder ./qa/screens \ "Sign in to staging with the saved test account. Buy the Pro yearly plan with the Stripe test card 4242 4242 4242 4242. Check the receipt page and the Paid badge in /admin, and save a screenshot of each step."03
Find cookies set before consent
“Make a new workspace for each run, one with staging.example.com/?geo=de and one with ?geo=us. Before any click, read document.cookie with evaluate and list the cookies set before consent. Check that Reject all is on the first layer for the EU.”
04
Follow a reset mail
“Request a password reset for qa@example.com. Open the Mailpit inbox on staging, click the link in the mail and check that it opens the reset form on staging.”
05
Check it each night
cuiar routines create "Nightly reset" --schedule "0 2 * * 1-5" --time-zone Europe/Berlin \ --workspace qa-reset --webhook https://ci.example.com/hooks/cuiar \ "Request a password reset on staging for the test account, open the reset link from the staging mail viewer, set a new password and report each step that fails."The result comes by email, and a signed webhook goes to CI.
Good to know
- Permission modes
- Grok Build asks by default. In auto mode a classifier approves safe tools. Deny rules always win.
- Access
- Grok Build is an early beta for SuperGrok and X Premium Plus subscribers.
- Headless
grok -p "..." --output-format jsonruns it from CI.
Templates to run from Grok Build
All templatesEach template page shows the run_task or create_routine call to give Grok Build.
Engineering
Run a smoke test on staging after each deploy
Sign-in, key pages and main actions checked in the browser, with a screenshot of each failure.
On an event: When a new staging deploy finishes- Vercel
- Any website
EngineeringAsks first
Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
You start it: When you start it- GitHub
Engineering
List pull requests that wait for review
Open PRs across your repos with age, reviewers and CI status, the oldest first.
On a schedule: Every weekday at 10:00- GitHub
Engineering
Compare staging with production before a release
Text, layout and console differences page by page, with the ones that look like bugs marked.
You start it: When you start it- Any website
- Google Docs
EngineeringAsks first
Draft status page updates during an incident
A clear update from the incident channel and your monitors, posted to your status page after you approve it.
You start it: When you start it- SSlack
- Datadog
- Any status page
Data
Pull tables from PDFs into a spreadsheet
Each matching table from your PDFs and scans in one sheet, with numbers as numbers and the page noted.
You start it: When you start it- Google Drive
- Google Sheets
More agents
All AI agentsClaude CodeRemote MCPTest real flows from the terminal
CodexRemote MCPconfig.toml, codex exec and nightly checks
CursorRemote MCPCheck localhost in a real tab
Kimi K3Remote MCPListings and supplier data into CSV
ChatGPTRemote MCPErrands from a chat, with your OK on each click
OpenAI dotsCLIAn always-on dot, through your own computer
Start on the Free plan.
The MCP server, the vault and unlimited routines are free. Steps that your own agent takes use no Cuiar credits.