01 · Records and state owned
JSON-based Qualtrics APIs including surveys, responses, contacts, and XM Directory where licensed.
Qualtrics
Qualtrics XM
A major enterprise research and experience-management system with broad APIs and SDKs for surveys, directories, responses, workflows, reporting, and governed program data.
Research, forms & feedbackSystem of intelligenceExtensible SaaS
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.
02 · Data you can retrieve
Use tools generated from licensed JSON API endpoints to query Qualtrics resources such as survey response rates, responses, contacts, and XM Directory data.
03 · Actions and write paths
Run create, update or removal operations exposed by licensed JSON API endpoints, including supported XM Directory contact updates.
04 · Authentication and permissions
Underlying API access requires the licensed API feature and products, a user with Access API permission, and the correct data-center endpoint. Qualtrics documents per-user X-API-TOKEN and client-credentials OAuth for API use; confirm transport-specific MCP setup.
05 · Monitoring, approval, and recovery
Use a dedicated least-privilege API user, keep survey responses and directory contacts within brand and product access boundaries, and require confirmation before contact, survey, response, or account mutations.
06 · Limits and caveats
MCP covers documented JSON-based APIs only; non-JSON APIs are unsupported. API access is a licensed feature, usable only for products in the license, and regenerating a user's token irreversibly invalidates the previous token.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverQualtrics API-generated MCP serversCurrent documented service
Support: Official MCP server
Read scope: JSON-based Qualtrics APIs including surveys, responses, contacts, and XM Directory where licensed.
Write scope: API update operations are exposed where the underlying JSON API supports them.
Authentication: Underlying APIs use a per-user X-API-TOKEN against the correct data-center endpoint; client-credentials OAuth is also documented, while MCP-specific connection credentials require confirmation.
Approval boundary: Require confirmation before any JSON API tool changes contacts, surveys, responses, users, or other governed XM program data.
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 access4
Event access1
Identity4
Governance4
Agent access4
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 Qualtrics ships them.
Single-platform patterns
- Enterprise research and experience-insight room
- Research synthesis room
- Feedback triage console
- Evidence-backed insight brief
Multi-platform compositions
- Qualtrics XM + CRM or product analytics: research synthesis room
- Qualtrics XM + work and knowledge system + content or planning platform: cross-system decision workspace
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.qualtrics.com/support/integrations/api-integration/overview/ ↗Qualtrics states that it provides an MCP server for each documented JSON-based API, exposing a tool for each supported API endpoint.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
API platformSource inventory
https://api.qualtrics.com/ ↗First-party API documentation and SDK guidance.
- 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.qualtrics.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.