mcpField
Q
QualiTaTi

QualiTaTi

Remote
qualitati.comBusiness & Marketing0Updated 6w ago

About QualiTaTi

QualiTaTi for AI agents connects MCP clients to QualiTaTi's hosted research platform for interviews, conversational surveys, and qualitative analysis. Its plugin also supplies workflow skills and slash commands.

Key features

  1. 01Create and manage interview studies
  2. 02Read and import interview transcripts
  3. 03Run qualitative analysis
  4. 04Build and publish conversational surveys
  5. 05Workflow skills and slash commands

Use cases

  1. 01Setting up an interview study
  2. 02Creating a conversational survey
  3. 03Reviewing transcripts and analysis results

MCP support

Connects clients to QualiTaTi's hosted MCP server, which exposes tools for projects, interviews, analysis, and surveys. Clients can authenticate with an API key or supported MCP authorization.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.qualitati.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.qualitati.com/mcpAuth required

Tools

Details

From the project README

QualiTaTi for AI agents

Run AI-moderated interviews, conversational surveys and qualitative analysis on QualiTaTi from Claude Code, Codex, OpenCode, Cursor, Claude Desktop or any MCP client.

One hosted MCP server does the work; this repo packages it as an installable plugin for the tools that have plugin systems and documents the one-line config for the rest. The plugin adds three skills that teach the agent QualiTaTi's workflows (setting up an interview study, building a survey, reading results) and two slash commands.

Prerequisites

  1. A QualiTaTi account — free tier is fine.
  2. A personal API key: qualitati.com → Profile → API keys (keys start with qt_). The key inherits your plan, quotas and billing; revoke it there any time.
  3. Put it in your shell: export QUALITATI_API_KEY=qt_…

Clients that implement MCP authorization (OAuth 2.1 with dynamic client registration) can skip the key entirely: point them at the server URL and a QualiTaTi consent page opens in your browser. Claude Code: claude mcp add --transport http qualitati https://api.qualitati.com/mcp, then /mcp → Authenticate.

Install

Claude Code
/plugin marketplace add lanceyuu/qualitati-agent-plugins
/plugin install qualitati@qualitati-agent-plugins

You get the qualitati MCP server (reads QUALITATI_API_KEY), the skills, and /qualitati:new-study and /qualitati:results. Without the plugin, the server alone:

claude mcp add --transport http qualitati https://api.qualitati.com/mcp \
  --header "Authorization: Bearer $QUALITATI_API_KEY"
Codex CLI / app
codex plugin marketplace add lanceyuu/qualitati-agent-plugins
codex plugin add qualitati@qualitati-agent-plugins

Or configure the server directly in ~/.codex/config.toml:

[mcp_servers.qualitati]
url = "https://api.qualitati.com/mcp"
bearer_token_env_var = "QUALITATI_API_KEY"
OpenCode
{
  "mcp": {
    "qualitati": {
      "type": "remote",
      "url": "https://api.qualitati.com/mcp",
      "enabled": true,
      "headers": { "Authorization": "Bearer {env:QUALITATI_API_KEY}" }
    }
  }
}
Cursor

.cursor/mcp.json (or use the Add to Cursor button on https://qualitati.com/developers):

{
  "mcpServers": {
    "qualitati": {
      "url": "https://api.qualitati.com/mcp",
      "headers": { "Authorization": "Bearer qt_your_key_here" }
    }
  }
}
Claude Desktop

Custom connectors cannot send a fixed header yet, so bridge with mcp-remote in claude_desktop_config.json:

{
  "mcpServers": {
    "qualitati": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.qualitati.com/mcp",
               "--header", "Authorization: Bearer qt_your_key_here"]
    }
  }
}
MCP Registry

Listed as io.github.lanceyuu/qualitati on the official MCP Registry (server.json in this repo), so registry-aware clients and directories find it without any of the above.

What the agent can do

ToolWhat it does
project_list, project_get, project_create, project_sharefind or set up an interview study and get the participant link
project_interviews, interview_get, interview_importsee completion status, read full transcripts, import external transcripts
analysis_run, analysis_results, analysis_summary, analysis_digestrun and read quality + coding analysis, digests, counts
survey_create, survey_add_question, survey_publishbuild a conversational survey and publish it

A human participant still conducts the interview via the share link; the agent sets studies up and reads the results.

Repo layout

One plugin, two package layouts, shared skills:

.claude-plugin/marketplace.json     Claude Code marketplace (this repo, plugin source "./")
.claude-plugin/plugin.json          Claude Code plugin manifest
.agents/plugins/marketplace.json    Codex marketplace (this repo, plugin path "./")
.codex-plugin/plugin.json           Codex plugin manifest (mcpServers -> ./mcp.json, so Codex reads the bearer_token_env_var form)
plugin.json  mcp.json               Codex / Agent Plugins (Open Plugins) manifest + MCP config
.mcp.json                           Claude Code MCP config
skills/  commands/  assets/         shared
server.json                         MCP Registry entry

The repo root is the plugin (the Open Plugins layout cursor.directory scans), and the two marketplace files let Claude Code and Codex install it from the same repo.

License

MIT. QualiTaTi is a product of QualiTaTi ([email protected]).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.