Book free pilot
Book free pilot

Connect Hallway Test to Cursor

Cursor talks to remote MCP servers over HTTP and handles the OAuth sign-in for you. Add one entry to mcp.json, authorize once, and the 11 Hallway Test tools show up in Agent mode.

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

Add the server in Cursor

About three minutes, including the sign-in.

  1. 01

    Open the MCP configuration

    In Cursor, open Cursor Settings and go to the MCP section, then choose Add new MCP server. Or edit the file directly: ~/.cursor/mcp.json makes the server available in every project, .cursor/mcp.json inside a repository limits it to that project.

  2. 02

    Add Hallway Test

    Paste this entry. There are no headers or API keys to fill in: Hallway Test uses OAuth, so Cursor asks you to sign in instead.

    {
  "mcpServers": {
    "hallwaytest": {
      "url": "https://mcp.hallwaytest.ai/mcp"
    }
  }
}
  3. 03

    Sign in

    Back in the MCP list, Hallway Test shows a Needs login state. Click it: your browser opens the Hallway Test sign-in, sign in with Google and approve the connection. Cursor registers itself with the server automatically, so there is nothing to paste back.

  4. 04

    Check the tools

    Once the indicator next to the server turns green, expand it. You should see 11 tools, from plan_usability_test_suite to jam_get_network_requests. If the list stays empty, toggle the server off and on.

  5. 05

    Run your first test

    Open Agent mode and 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.
  6. 06

    You’re all set

    Cursor 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 Cursor 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

Update Cursor to the current version; some builds skipped the OAuth step for remote servers. Then remove the entry, add it again and click Needs login. Cursor receives the sign-in on http://localhost:8787/callback, so that port has to be free on your machine.

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.

The token has expired. Click the server in the MCP list and sign in again; your configuration stays as it is.

Yes. Commit .cursor/mcp.json to the repository. The entry contains only the server URL; every teammate signs in with their own Google account the first time.

Book free pilot