Book free pilot
Book free pilot

Connect Hallway Test to Codex

Codex supports remote MCP servers with OAuth out of the box. Two commands register Hallway Test and sign you in; the 11 tools are then available in every Codex session, in the terminal and in the IDE extension.

MCP endpoint: https://mcp.hallwaytest.ai/mcp · Also for Claude and Cursor · Last updated: September 26, 2026

Add the server in Codex

About three minutes, including the sign-in.

  1. 01

    Add the server from the CLI

    Run this in your terminal. Codex writes the entry to ~/.codex/config.toml.

    codex mcp add hallwaytest --url https://mcp.hallwaytest.ai/mcp
  2. 02

    Or add it to config.toml by hand

    The same entry in ~/.codex/config.toml. No token variable is needed: Hallway Test uses OAuth.

    [mcp_servers.hallwaytest]
url = "https://mcp.hallwaytest.ai/mcp"
  3. 03

    Sign in

    Codex opens your browser: sign in with Google and approve the connection. Codex registers itself with the server automatically, so no client ID is required.

    codex mcp login hallwaytest
  4. 04

    Check the connection

    codex mcp list shows hallwaytest with its URL. In a Codex session, ask What Hallway Test tools do you have? and you should get the 11 tools back.

    codex mcp list
  5. 05

    Using the IDE extension instead

    Open the gear menu, choose MCP servers, then Add server and Streamable HTTP. Enter hallwaytest as the name and https://mcp.hallwaytest.ai/mcp as the URL, restart the extension, and choose Authenticate when prompted.

  6. 06

    Run your first test

    Describe the flow in one sentence, for example:

    Use Hallway Test to have a real user place an order as a guest on https://staging.example.com and reach the confirmation page.
  7. 07

    You’re all set

    Codex calls create_usability_task and waits for the recording with wait_for_usability_result; results come back within 24 hours. When the session is ready, ask it to audit the recording and fix what the tester got stuck on.

Account activation. A new account can connect right away, but the first request to dispatch a test answers with a link to book the free pilot call. After the 30-minute call we activate the account and tests start immediately, with no need to reconnect. Book the pilot call.

MCP structure

Curious what Codex can actually call? See every tool this connector exposes, pulled straight from the live MCP server.

Stuck partway through? Talk to us →

If something does not work

The name must match the entry: codex mcp list shows the names Codex knows. If the entry is missing, check ~/.codex/config.toml for a typo in the [mcp_servers.hallwaytest] header.

Your account is connected but not activated yet. Activation happens on the free pilot call; book it through the link, and after the call every test dispatch goes through without reconnecting.

Run codex mcp login hallwaytest again. The configuration stays in place; only the sign-in is refreshed.

Yes, with one command: claude mcp add --transport http hallwaytest https://mcp.hallwaytest.ai/mcp. Claude Code opens the same Google sign-in.

Book free pilot