# Connect Hallway Test to Claude

> Step-by-step guide to add the Hallway Test MCP as a custom connector in Claude
> and start running real usability tests from your conversations.

Page: https://hallwaytest.ai/connect-mcp
MCP endpoint: https://mcp.hallwaytest.ai/mcp

Add the Hallway Test MCP as a custom connector, authorize it once, and Claude
can hand off usability tests whenever you ship something new.

## From the CLI

```
claude mcp add --transport http hallwaytest https://mcp.hallwaytest.ai/mcp
```

## From the Claude GUI

1. **Open Customize settings.** In Claude, open your workspace settings and
   click "Customize" — that's where all your connectors and integrations live.
2. **Go to Connectors.** Inside Customize, select the "Connectors" tab to see
   every MCP server currently linked to your workspace.
3. **Add a custom connector.** Open the "Add" menu and choose "Add custom
   connector" — this lets you connect an MCP server that isn't in Claude's
   built-in list.
4. **Enter the Hallway Test details.** Name it `Hallway Test` and paste the MCP
   URL: `https://mcp.hallwaytest.ai/mcp`.
5. **Save the connector.** Click "Add connector" to register Hallway Test with
   your workspace.
6. **Authorize access.** Sign in with your Google account when prompted, so
   Claude can securely talk to the Hallway Test MCP server on your behalf.
7. **You're all set.** Start a conversation, describe what you just shipped, and
   ask Claude to run a usability test with Hallway Test — no dashboards, no
   scheduling.

## What Hallway Test exposes to Claude

### Run a test

- `create_usability_task` — writes and dispatches a real usability test to a
  real user, based on the flow you describe.
- `wait_for_usability_result` — waits for the tester to finish and hands back the
  session recording as soon as it's ready.
- `cancel_test_run` — cancels a test that was already dispatched.

### Plan tests

- `plan_usability_test_suite` — scans your project and drafts a full test suite,
  5 to 10 critical user flows, ranked by risk.

### Analyze a recording

- `plan_jam_ux_audit` — turns a raw recording into a structured, evidence-backed
  UX audit by running the tools below in the right order.
- `jam_get_details` — recording metadata: type, duration, whether a voice
  transcript exists, and the shareable link.
- `jam_get_user_events` — the full click / type / navigation log, the source of
  truth for what the tester actually did.
- `jam_get_video_transcript` — the tester's spoken think-aloud commentary,
  timestamped.
- `jam_get_frames` — screenshots from key moments in the recording, to visually
  confirm a friction point.
- `jam_get_console_logs` — browser console logs, used to explain a technical
  cause behind friction that's already been proven.
- `jam_get_network_requests` — network request log, used to trace a failed call
  behind an already-evidenced UX problem.

## Stuck partway through?

Write to support@hallwaytest.ai.

## Related

- [Home](https://hallwaytest.ai/index.md)
- [Book a free pilot](https://hallwaytest.ai/book.md)
- [Connect Hallway Test to Cursor](https://hallwaytest.ai/connect-cursor.md)
- [Connect Hallway Test to Codex](https://hallwaytest.ai/connect-codex.md)