Understanding the MCP Server
| How to Connect |
| Authentication |
The Qualta MCP Server lets AI clients that speak the Model Context Protocol (MCP) — e.g. Claude Cowork, ChatGPT Work, custom agents — securely read a team's Qualta Guides and their Interviews as context. It is read-only: it retrieves and searches data; it never creates or changes anything.
How to Connect
Clients connect to the MCP server over streamable HTTP. Point your client's MCP configuration at the following endpoint:
https://qualta.io/mcp/qualta
Authentication
Authentication is required — an unauthenticated request is rejected (HTTP 401) with a challenge that tells compliant clients how to authenticate.
OAuth 2.1 (recommended)
Your client discovers the server's OAuth settings automatically. You will be redirected to a Qualta authorization screen to approve or deny access. On approval, the client receives an access token allowing it to call MCP tools and resources.
API Token
To access the MCP server programmatically, first generate an API token with the mcp:use permission (see How to Create an API Token), then send it as a bearer token on the Authorization header with each request.
When authenticating via API Token ensure the following request headers are set
Accept: application/jsonContent-Type: application/jsonAuthorization: Bearer <token>