Survey
UserTesting MCP connector
Connect UserTesting to Elaichi and Claude, ChatGPT, Cursor, and any MCP client can read your studies, session results, transcripts, clips, highlight reels, and QX scores, with each person signed in as themselves and every request logged.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect UserTesting to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect UserTesting once
-
Open Connections, choose Add connection, and pick UserTesting.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your UserTesting app credentials. UserTesting authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect UserTesting to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect UserTesting to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect UserTesting to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect UserTesting to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with UserTesting through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
UX Research
Write up a study the morning after
Ask for the session results and transcripts from a study that finished overnight and get a summary of where participants hesitated, what they said, and which tasks they failed.
-
Product
Compare QX scores before a launch decision
Pull the QX scores for every test on a feature and see whether the latest round of changes actually moved the numbers before you commit to a ship date.
-
Design
Find the exact moment a tester got stuck
Search the transcripts for the screen or word you care about, then jump to the session clip and video so you can watch what happened instead of guessing.
-
Marketing
Turn highlight reels into customer stories
List the highlight reels from recent tests, find the quotes where people describe the product in their own words, and reuse them for launch copy and case studies.
-
Support
Match tickets to what testers already said
When the same confusion keeps showing up in tickets, check whether UserTesting participants ran into it too, and hand the transcript to the product team as evidence.
-
Research Ops
See what every workspace is testing
List every UserTesting workspace and its studies to spot duplicated research, catch teams testing the same flow twice, and keep a running picture of what has been covered.
Try asking
- “Summarize last week's session results for the checkout study.”
- “Which studies have the lowest QX scores this quarter?”
- “Pull transcripts from the onboarding study and list top complaints.”
AI tools
UserTesting tools for your AI agents
13 tools are ready to call through Elaichi's MCP endpoint the moment you connect UserTesting, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting UserTesting gets you
6 screens from the product, each doing one job for your UserTesting account.
The agent
Ask about studies, get answers from sessions.
Type a question in plain language and read answers from live UserTesting studies.
- studies
- session results
- transcripts
- clips
Ask Elaichi to work across your apps.
Summarize last week's session results for the checkout study.
Which studies have the lowest QX scores this quarter?
Pull transcripts from the onboarding study and list top complaints.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Any MCP client connects over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
13 UserTesting tools, no custom code written.
Studies, session results, transcripts, clips, highlight reels and QX scores are covered already.
- List all UserTesting workspaces
- List all UserTesting workspace studies
- List all UserTesting studies
- Get single UserTesting study by ID
Toolboxes
Each team gets its own UserTesting toolbox.
Scope one toolbox to Research and another to Design, listed side by side.
- Research
- Design
- Product
- Marketing
Shared connections
Teammates read sessions without seeing a credential.
The connections table shows who connected each account and how many teams share it.
- Research EMEA
- Product Design
- Mobile App
- Growth
Audit log
Every transcript opened stays on the record.
An append-only log of when, who, what happened, type and resource per call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns sessions into an approved digest.
Fetch session results, group them, draft a digest, get approval, post back to UserTesting.
UserTesting digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch studies
UserTesting
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
UserTesting
Queued
Collections and dashboards
Study health is counted, never generated.
Four metrics, 14 days of studies created and a team breakdown, refreshed on schedule.
UserTesting health
Refreshed 4 minutes ago · every 15 minutes · from the studies collection
Studies
1,284 ↓ 12%
Session results
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Studies created
Last 14 days
By team
Share of activity
Research EMEA 34%
Product Design 27%
Mobile App 21%
Growth 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect UserTesting to Claude?
Connecting UserTesting to Claude takes two steps. First, connect UserTesting in Elaichi by pasting the app credentials from your UserTesting account, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Claude can start reading your studies and session results.
Does UserTesting work with ChatGPT and Cursor as well as Claude?
Yes. Once UserTesting is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect UserTesting once and every client you use picks it up.
What can an AI agent actually do with my UserTesting data?
With UserTesting connected, an AI agent can list your workspaces and studies, open a specific study, and read its session results, transcripts, clips, highlight reels, and QX scores. In practice that means asking things like which tasks participants failed in last week's study, what people said when they reached the checkout page, or how the QX score changed between two rounds of testing. It can also give you the video download links for a session so you can watch it yourself.
Does connecting UserTesting give the AI access to every workspace?
No. Access follows the person who signed in, so the AI only sees the UserTesting workspaces, studies, and sessions that person can already open in UserTesting. Elaichi can narrow that further, for example to a single workspace or to results without video links, but it never widens it beyond what the person already has.
Can I stop an AI agent from changing or deleting things in UserTesting?
The UserTesting connector only reads: it lists and opens studies, session results, transcripts, clips, highlight reels, and QX scores, and cannot create, edit, or delete anything in UserTesting. If you want to go further, Elaichi restrictions work per action, so you can block access to session video links or clips for a given team. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.
What happens to a UserTesting connection when someone leaves?
When you offboard someone in Elaichi, their access to UserTesting through every client ends at once, including Claude, ChatGPT, and Cursor. A UserTesting connection they shared with a team keeps working for everyone else on that team. If you ever want to remove UserTesting entirely, disconnecting it once in Elaichi removes it from every client.
Put UserTesting in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.