UserTesting

UserTesting

UserTesting's limited-early-access MCP brings human insight into AI clients and supports participant recruiting, study creation, test launch, and results-informed product workflows.

Research, forms & feedbackSystem of intelligenceExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of intelligence
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Workspaces, studies, target-audience criteria, participants recruited through UserTesting and User Interviews, launched tests, results, qualitative insight, and customer verbatims.

02 · Data you can retrieve

Bring available UserTesting results, qualitative insight, and customer verbatims into supported AI workflows for analysis, comparison, design context, and decision support.

03 · Actions and write paths

Create studies, recruit participants, and launch tests through supported tools.

04 · Authentication and permissions

UserTesting documents secure authentication and workspace-level controls. MCP access is currently limited to selected early-access teams.

05 · Monitoring, approval, and recovery

Before action, show the workspace, study design, target audience, recruiting source, participant criteria, and launch state. Keep participant consent, evidence access, and human review attached to returned insight.

06 · Limits and caveats

Limited early access is available only to selected teams. The public page does not enumerate the tool catalog, plan eligibility, rate limits, detailed permission mapping, or client-specific setup.

Agent access

MCP support

Official MCP serverUserTesting MCP serverLimited Early Access

Support: Official MCP server

Read scope: Use available results, qualitative insight, and customer verbatims as context for analysis, design generation, validation, and product decisions.

Write scope: Create studies, recruit participants, and launch tests through supported tools.

Authentication: Secure UserTesting authentication through a supported AI-client connection; the public page does not specify the exact flow.

Approval boundary: Require explicit review of target audience, participant criteria, study design, recruiting source, and final launch before creating a live research engagement.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access2
Event access1
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability3
Documentation2

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that UserTesting ships them.

Single-platform patterns

  • Customer evidence review and decision room
  • Research synthesis room
  • Feedback triage console
  • Evidence-backed insight brief
Use in the brief builder →

Multi-platform compositions

  • UserTesting + CRM or product analytics: research synthesis room
  • UserTesting + work and knowledge system + content or planning platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

3 recorded sources
MCP / agent-role validationRepresentative source
https://www.usertesting.com/platform/mcp-server ↗

UserTesting documents limited early access for recruiting participants, creating studies, and launching tests.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

Developer portalSource inventory
https://developer.usertesting.com/ ↗

First-party API and embedding documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.usertesting.com/ ↗

Product overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.