Connect Claude, Grok, and Codex to Validate.QA
Add Validate.QA as a remote MCP connector in Claude, Grok, Grok Bot, or Codex — OAuth, no PAT, same 48 tools as the dashboard.
You can now Connect Validate.QA from Claude, Grok, Grok Bot, and Codex the same way you add any other remote MCP connector — no personal access token, no npx, no JSON file. Sign in once, pick a project, and the assistant gets the same 48 tools the dashboard uses: discovery, generation, runs, healing, schedules, security findings.
That is a different path from the IDE package @validate.qa/mcp. Cursor, Claude Code, and Codex CLI still use that stdio server with a pat_ token. Chat apps and connector catalogs speak Streamable HTTP to /mcp and complete OAuth. Mixing the two is the usual setup failure.
What you get after Connect
The hosted connector is the same tool surface as the IDE server: create and edit tests, run discovery, heal failures, read live project state. The assistant does not invent a second runtime. It asks Validate.QA to execute Playwright on your runner, then reads the result back into the conversation.
Auth is OAuth 2.1 with PKCE. After you Allow, the client holds an mcp_at_ access token scoped to you plus one project. It is not a runner token and not a PAT.
Claude Desktop and claude.ai
Open Customize → Connectors → Add custom connector. Paste the URL from Project Settings. Connect. Complete the consent screen. On the next Claude session the Validate.QA tools are available in that project context.
Claude Code in the terminal is still the stdio package — see the IDE MCP guide . Use Connectors for Desktop / claude.ai; use claude mcp add for the CLI.
Grok and Grok Bot
On the web: grok.com/connectors → New Connector → Custom → paste the same /mcp URL. Grok Build TUI is not grok.com Connectors — adding a connector on the website does not log the CLI in. Use the TUI's own MCP config if you work in the terminal.
Grok Bot: Settings → Plugins → custom MCP URL. Same hosted endpoint, same OAuth consent.
Codex
Codex's connector catalog takes the hosted URL. Add a custom MCP server, paste {'/mcp'}, connect, finish consent. Codex CLI in a repo still prefers the stdio package with a pat_ — same pattern as Claude Code versus Claude Desktop.
Topics: MCP, Claude, Grok, Codex, Connectors.
Read the full article · Get Started Free