1. Knowledge Base Home
  2. UserTesting
  3. UserTesting Integrations
  4. UserTesting MCP

Connect the UserTesting MCP to your AI client (Open beta)

Connect your UserTesting account to Claude, ChatGPT, Cursor, Figma Make, or another AI client using the UserTesting MCP. Once connected, you can create, launch, and read UserTesting tests without leaving your AI client. 

 

Product: UserTesting
Experience: New

 

On this page:

 

 

Before you connect

Note: The UserTesting MCP is in open beta. Your account does not need to be enabled or opted in to connect. Accounts that have opted out of Generative AI features are excluded — see Introducing the UserTesting MCP (Open beta)

Confirm you have:

Requirement Details
A supported AI client, installed Claude Code, Claude Desktop or Web, ChatGPT, Codex CLI or Desktop, GitHub Copilot CLI, Cursor, Visual Studio Code, Amazon Kiro, Gemini CLI, Antigravity IDE, or Figma Make
A UserTesting sign-in Customer login and employee SSO both work. Authentication is per user; there is no shared or service-account login

WRITE or ADMIN permission in a workspace

to create tests

 Your UserTesting permissions carry over unchanged. With READ, you can still connect, find tests, and read AI summaries
An admin, for some clients Claude Desktop and Web, ChatGPT, and Figma Make need a workspace or organization admin to add the connector once. The steps are included in each of those sections

 

You do not need a saved audience to connect, and you do not need one to create every kind of test - see Create and launch a test with the UserTesting MCP (Open beta).

 

The UserTesting MCP server URL

All clients connect to the same URL: https://ai.usertesting.com/mcp

No client ID or client secret is required. If your client's configuration has an OAuth client ID or client secret field, leave it empty. Clients either register themselves automatically using Dynamic Client Registration, or identify themselves through a Client ID Metadata Document — Claude, Claude Code, ChatGPT, and Visual Studio Code all do this.

Expect a consent screen. The first time you connect from a given client, you are prompted to authorize the connection. Accept it. It appears once per client.

Sign in with your normal UserTesting credentials. Customer login and employee SSO both work.

 

Connect your AI client

Find your client in the list of sections on this page. Each set of steps is self-contained. A connection made in one client does not carry over to another — a terminal connection and a desktop connection are configured separately, even for the same product.

 

Claude Code (CLI or IDE extension)

Use these steps whether you run Claude Code from the command line or as an IDE extension. To install Claude Code, see https://code.claude.com/docs/en/quickstart.

Click here to view instructions
  1. Add the server. Run in your terminal:
    claude mcp add --transport http usertesting "https://ai.usertesting.com/mcp"
    Discovery is automatic, and no client ID is needed. If authentication fails with a redirect or callback error, run the command again with --callback-port 8080.
  2. Start Claude Code, run /mcp, select usertesting, and choose Authenticate. A browser window opens to complete your UserTesting sign-in, followed by a consent screen — accept it.
  3. Confirm the connection. Run claude mcp list. usertesting appears with a connected status.

Tip: If the browser does not open, copy the URL printed in the terminal and paste it into a browser manually.

 

Claude (Desktop and Web)

UserTesting is not yet listed in the Claude Connectors marketplace, so Claude Desktop and the web app connect through a custom connector. Adding a custom connector requires an IT or workspace admin.

Click here to view instructions

Admin — add the connector, once:

  1. In the Claude admin or workspace settings, go to Connectors.
  2. Select Add connector.
  3. Name it UserTesting Production MCP.
  4. Paste the server URL: https://ai.usertesting.com/mcp
  5. Leave the OAuth Client ID and Client Secret fields empty. Claude identifies itself automatically; no manual registration is needed.
  6. Save the connector.

Individual Users — connect:

  1. Go to Customize → Connectors at claude.ai/customize/connectors in Claude Desktop or on the web.
  2. Select UserTesting Production MCP and click Connect.
  3. Sign in and accept the consent screen.
  4. Pre-approve the actions you want, or approve them one call at a time.

Note: Once UserTesting is listed in the Claude Connectors marketplace, you will be able to add it directly without a custom connector.

 

ChatGPT

Click here to view instructions

Admin — add the connector, once:

  1. In the ChatGPT workspace admin settings, add a new connector or app.
  2. Enter the server URL: https://ai.usertesting.com/mcp
  3. Leave the OAuth Client ID and Client Secret fields empty. ChatGPT registers itself automatically.
  4. Save.

Individual Users — connect:

  1. Go to https://chatgpt.com/apps.
  2. Select UserTesting Production MCP and click Connect.
  3. Sign in, accept the consent screen, and click Continue.
  4. Click Start chat.

 

Codex CLI

Run in your terminal, then complete the sign-in and consent screen when prompted:

codex mcp add usertesting --url https://ai.usertesting.com/mcp

 

Codex Desktop

  1. Open the Codex Desktop MCP settings and add a server.
  2. Set the name to Usertesting-mcp-pro and the transport to streamable HTTP.
  3. Enter the server URL: https://ai.usertesting.com/mcp
  4. Complete the sign-in and consent screen when prompted.

 

Figma Make

Figma Make connects through a custom connector that a Figma organization admin publishes once for the whole organization. There is no per-user configuration file, and individual users do not add anything themselves. Figma Make is available on Figma Organization and Enterprise plans only.

Click here to view instructions

Admin — enable custom connectors first:

Under Admin → Settings → AI → Connectors in Figma Make, enable Allow custom connectors. AI features must also be enabled organization-wide; if AI is off, connectors are off.

Admin — create and publish the connector:

  1. In a Figma Make file, click Add context, hover over Connectors, then select Manage.
  2. On the Created by you tab, click Create.
  3. Enter the Name: UserTesting MCP. Optionally add an icon, tagline, and description.
  4. Enter the MCP server URL: https://ai.usertesting.com/mcp
  5. Leave Advanced settings empty. No client ID or client secret is required.
  6. Click Create, then Connect to authenticate.
  7. Review the Read and Write actions and enable the ones you want exposed. Write actions are disabled by default — leave them off and no one in the organization can create or launch a test through Figma Make.
  8. Click More → Publish, review, select the confirmation checkbox, and click Publish. The connector then appears for everyone in the organization under the organization tab of the connectors modal.

Individual Users — use it: in the Figma Make chat, type @ and select the UserTesting connector, or paste a UserTesting reference and let Figma AI pick it up. If Figma AI does not pull it in automatically, reference it explicitly with @.

Note: Authentication is still per user. Each person signs in to their own UserTesting account the first time they use the connector, and their UserTesting permissions apply.

 

GitHub Copilot CLI

Click here to view instructions
  1. Edit ~/.copilot/mcp-config.json and add the server:
    {
      "mcpServers": {
        "usertesting": {
          "type": "http",
          "url": "https://ai.usertesting.com/mcp",
          "tools": ["*"],
          "auth": {
            "redirectPort": 8080
          }
        }
      }
    }
  2. Restart Copilot and complete the sign-in and consent screen when prompted.

Note: Keep redirectPort: 8080. [NEEDS CONFIRMATION: whether a specific callback port is still required — the UserTesting MCP now accepts self-registering clients, which supply their own callback URL. Confirm with the MCP engineering team before publishing this instruction.]

 

 

Cursor

Click here to view instructions
  1. Edit your Cursor MCP configuration and add the server. Use ~/.cursor/mcp.json to make the server available in every project, or .cursor/mcp.json inside a project folder for that project only:
    {
      "mcpServers": {
        "usertesting": {
          "url": "https://ai.usertesting.com/mcp"
        }
      }
    }
  2. Open Cursor → Settings → MCP, find usertesting in the list, and select Needs login to complete your UserTesting sign-in in the browser.

Note: The global file (~/.cursor/mcp.json) and the project file (.cursor/mcp.json) are configured separately. If both define usertesting, the project file wins for that project.

 

 

 

Visual Studio Code

Click here to view instructions
  1. Open the command palette with Cmd+Shift+P and select MCP: Open User Configuration, or edit mcp.json directly. Add:
    {
      "mcpServers": {
        "usertesting": {
          "url": "https://ai.usertesting.com/mcp"
        }
      }
    }
  2. Save the file, then complete the sign-in and consent screen when prompted.

Tip: If you see errors after authenticating, restart the server using the controls beside the server name in the MCP view.

 

 

Amazon Kiro

Click here to view instructions
  1. Add the server to .kiro/settings/mcp.json for one workspace, or ~/.kiro/settings/mcp.json to apply it everywhere:
    {
      "mcpServers": {
        "usertesting": {
          "url": "https://ai.usertesting.com/mcp",
          "disabled": false
        }
      }
    }
  2. Click the Kiro icon in the left-hand side panel, select MCP, and authenticate the server.

Note: Keep "disabled": false or the server will not load. The workspace file and the user file are separate.

 

 

Gemini CLI

To install the Gemini CLI, see https://geminicli.com/docs/get-started/installation/. Sign in with your Google account first.

Click here to view instructions
  1. Set the callback port. Run in your terminal:
    export OAUTH_CALLBACK_PORT=8080
    [NEEDS CONFIRMATION: whether this step is still required. The Gemini CLI otherwise picks a random callback port. Confirm with the MCP engineering team whether the UserTesting MCP still requires a fixed port.]
  2. Add the server to ~/.gemini/settings.json:
    "mcpServers": {
      "usertesting": {
        "httpUrl": "https://ai.usertesting.com/mcp",
        "oauth": {
          "redirectUri": "http://localhost:8080/oauth/callback"
        }
      }
    }
  3. Authenticate in Gemini:
    /mcp auth usertesting

 

 

Antigravity IDE

Click here to view instructions
  1. Add the server to ~/.gemini/config/mcp_config.json:
    {
      "mcpServers": {
        "usertesting": {
          "serverUrl": "https://ai.usertesting.com/mcp"
        }
      }
    }
  2. Complete the sign-in and consent screen when prompted.

 

 

Connect an AI client that isn't listed

Most AI clients that support the Model Context Protocol automatically register with UserTesting the first time you connect, so they work with the server URL alone and require no setup on the UserTesting side. Try the URL first.

Contact UserTesting only if your client cannot register itself, which covers two cases:

  • A custom or in-house AI client your team built.
  • A client that requires a fixed callback or redirect URL to be registered in advance.

In either case, email support@usertesting.com and include:

  • The name of the AI client.
  • Its callback or redirect URL, including the port and path.
  • Whether it supports Dynamic Client Registration, if you know.

Until the client is configured, sign-in fails, and the client reports that it is not a recognized MCP client.

 

Verify the connection

Once you have authenticated, send a prompt in your AI client. Any of these confirms the connection is live:

  • Show me my UserTesting accounts.
  • What tests have recently completed in UserTesting, and which have an AI summary?
  • Create a draft UserTesting test to evaluate customer sentiment about our mobile app experience.

If the client returns your account list, the UserTesting MCP is connected.

If it returns No Accounts with Generative AI and MCP access enabled, the connection worked, but your UserTesting account has opted out of Generative AI features. Ask your UserTesting account admin to enable them.

 

Remove the UserTesting MCP from your client

Removing the connection revokes the client's access. Your tests and drafts in UserTesting are unaffected.

Client How to remove it
Claude Code (CLI) Run claude mcp remove usertesting
Claude Code (IDE extension) Run /mcp, select the server, and choose Disable
Claude Desktop or Web Settings → Connectors, select the connector, and disconnect
ChatGPT Disconnect the app at https://chatgpt.com/apps
Cursor, Visual Studio Code, Amazon Kiro, Copilot CLI, Gemini CLI, Antigravity Delete the usertesting entry from that client's MCP configuration file
Figma Make The organization admin unpublishes or deletes the connector

 

FAQ

Does my account need to be opted into the beta?

Yes. To request access to the MCP, contact Alison Held at aheld@usertesting.com. 

I see an invalid client error, or sign-in fails immediately.

Your client configuration contains an OAuth client ID. The UserTesting MCP does not use one. Remove the clientId, CLIENT_ID, or --client-id value from your configuration, clear the client's cached authentication, and connect again.

I get a callback or redirect mismatch error at sign-in.

Pin the callback port to 8080 using your client's callback-port setting — --callback-port 8080 in Claude Code, redirectPort in Copilot CLI, OAUTH_CALLBACK_PORT in Gemini CLI. If your client cannot set its callback port or path, email support@usertesting.com with the client name and its callback URL.

My client was rejected as an unrecognized MCP client.

The client could not register itself with UserTesting. Email support@usertesting.com with the client name and its callback or redirect URL — see Connect an AI client that isn't listed.

A consent screen appeared. Is that right?

Yes. It appears once per client, the first time you authorize it. Accept it.

I see Blocked by team admin.

Your AI client's workspace admin has to approve the UserTesting MCP before you can connect. This is a setting in your AI client, not in UserTesting.

I set it up in the terminal, but it didn't show up in Claude Desktop.

Expected. A terminal connection and a Desktop connector are configured separately. Set up Desktop through Settings → Connectors.

Do I have to authenticate again later?

Sessions expire based on your organization's token settings. If your AI client reports that it cannot reach UserTesting data, authenticate again the same way you first connected.

Can I use the UserTesting API instead?

For reading results, yes. Creating a test is available through the UserTesting MCP only. Reading results — session transcripts, session details, and quantitative data — is already available through the UserTesting API.

Who do I contact about a problem?

Email support@usertesting.com.

 

Related content

information icon.png

knowledge icon.png

Want to learn more? Check out these Knowledge Base articles... 

Interested in growing your skills? Check out our University courses...

video icon 2.png

team icon.png

Need hands-on training?

Can't find your answer?
Was this article helpful?

Articles in this section