The Qualtrics MCP Server provides a comprehensive interface to the Qualtrics API via the Model Context Protocol (MCP). It exposes a broad set of tools across eight domains—Surveys, Questions, Blocks, Survey Flow, Responses, Contacts, Distributions, Webhooks, and Users—so Claude can perform end-to-end survey management, from building surveys and questions to distributing them, exporting responses, and automating workflow steps. Typical use cases include creating and updating surveys, crafting questions (including simplified helpers for multiple-choice, text entry, and matrix questions), configuring the survey flow with embedded data and web services, exporting responses with smart filtering, managing mailing lists and contacts, sending email distributions and reminders, and subscribing to webhook events. The server also supports a read-only mode for safe exploration and a rich set of environmental configurations to tailor access and behavior.

To use it, configure Claude’s integration as described in the Claude Desktop Integration section, ensuring the MCP server is reachable and properly authenticated. Once running, you can issue natural-language prompts like: create a survey named “Customer Satisfaction Q1 2026,” add a 5-point Likert matrix question, set up a randomizer, or export all complete responses from the last 30 days. The tool layer translates these prompts into Qualtrics API calls, with built-in helpers to simplify common tasks (e.g., add_multiple_choice_question, add_embedded_data, or create_email_distribution).

Prerequisites:

• Node.js 22+ (or the environment you plan to run the MCP server in)
• pnpm (as recommended by the repository) or npm
• Qualtrics API token with appropriate permissions
• Qualtrics data center ID

Installation steps:

1. Clone the repository: git clone https://github.com/yrvelez/qualtrics-mcp-server.git
2. Navigate into the project: cd qualtrics-mcp-server
3. Install dependencies (pnpm recommended): pnpm install

   or npm install if you prefer

4. Create and configure environment variables: cp .env.example .env

   Edit .env with your Qualtrics credentials (API token, data center, etc.)

5. Start the MCP server locally (example using npx and tsx as per integration guidance): npx tsx path/to/qualtrics-mcp-server/src/index.ts

Configuration notes:

• Ensure QUALTRICS_API_TOKEN and QUALTRICS_DATA_CENTER are set in the environment or in the .env file.
• If you are integrating with Claude Desktop, add the server entry to claude_desktop_config.json as shown in the README. The command typically uses npx with tsx to run the index.ts file and points to your local path.

Environment variables:

• QUALTRICS_API_TOKEN: Your Qualtrics API token. Keep it secret.
• QUALTRICS_DATA_CENTER: Data center ID (e.g., yul1).
• QUALTRICS_BASE_URL: Optional; override base URL if needed.
• QUALTRICS_READ_ONLY: Set to true to block all write/update/delete operations at runtime.
• RATE_LIMITING_ENABLED / RATE_LIMIT_RPM: Control rate limiting behavior.
• REQUEST_TIMEOUT: Timeout in milliseconds for API requests.

Common issues and tips:

• Ensure the Qualtrics API token has the necessary permissions for the actions you intend to perform.
• If you encounter rate limiting, adjust RATE_LIMIT_RPM or enable/adjust rate limiting in the config.
• When using read-only mode, verify that all write operations are blocked by attempting a small test build or export.
• For Claude integration, ensure the path to your src/index.ts is correct in the command and that environment variables are exposed to the running process.