> ## Documentation Index > Fetch the complete documentation index at: https://docs.userintuition.ai/llms.txt > Use this file to discover all available pages before exploring further. # User Intuition MCP Server > Give an AI agent the tools and rules to design studies, recruit participants, manage interviews, and analyze findings. User Intuition's MCP server exposes the complete research workflow to AI agents: **50 tools on every transport**, covering the versioned public API plus account context, catalogs, interview usage, and a read-only study review app. ## MCP tools and Skills The MCP server gives an agent the **tools**. A User Intuition Skill gives it the **workflow**: when to ask for Panel versus BYOP recruitment, how to conduct the Customize Plan conversation, when to dry-run cost, and when confirmation is required. Configure Claude, Cursor, VS Code, or ChatGPT and verify the connection. Teach your agent a repeatable study-creation or analysis workflow. ## One surface on every transport For read-only exploration in Claude's directory, use the separate [Claude directory research connector](/mcp-server/claude-directory). * **Streamable HTTP** accepts OAuth for interactive clients and organization API keys for headless clients. Connect to `https://mcp.userintuition.ai/mcp`. * **stdio** remains available for Claude Desktop, Cursor, Claude Code, VS Code, and other local clients. It authenticates with a `ui_sk_` API key. Both transports expose the same 50 tools. Choose the authentication method that fits the client. ### Smaller profiles For the common study → interview → report workflow, connect to `https://mcp.userintuition.ai/core/mcp` (33 tools). It omits webhook, feasibility, external-panel, and platform-admin administration. For existing research without write actions, connect to `https://mcp.userintuition.ai/read-only/mcp` (25 tools). The `https://mcp.userintuition.ai/compact/mcp` profile keeps the research workflow and groups less common webhook, feasibility, and external-panel operations into 41 tools. Each URL has its own OAuth protected-resource metadata, so authorize the specific URL your client uses. The full `/mcp` URL remains available for all 50 tools. Local stdio clients can pass `--profile core`, `--profile read-only`, or `--profile compact` after the package name. The default is the full profile. Resource and prompt support remains available on these profiles. Measured from the complete `tools/list` response in the cited-answer and cursor MCP change set: | Profile | Tools | Payload bytes | Approx. tokens | | - | -: | -: | -: | | Full | 50 | 121,538 | 30,385 | | Core | 33 | 88,649 | 22,162 | | Read-only | 25 | 67,216 | 16,804 | | Compact | 41 | 106,850 | 26,713 | | Directory | 8 | 31,752 | 7,938 | The token estimate divides bytes by four; actual model context usage varies by host and tokenizer. CI checks each profile against its payload budget. ## Tool groups | Group | Tools | What it covers | | - | -: | - | | Account | 2 | Effective workspace, payment readiness, and platform-admin organization search | | Studies | 20 | Create, customize, review, estimate, launch, pause, stop, report on, search, and answer questions across studies | | External panels | 4 | Configure a customer-supplied panel bridge for a BYOP study | | Participants | 7 | Create and manage BYOP invitations and rewards | | Interviews | 4 | Read or delete interviews and inspect usage | | Panel feasibility | 4 | Specialist feasibility review | | Webhooks | 8 | Create, inspect, test, and remove event subscriptions | | Configuration & catalogs | 1 | Targeting attributes; other catalogs are MCP resources | The [tool reference](/mcp-server/tools/studies) documents every registered tool. The [study-creation playbook](/mcp-server/guides/playbook) documents the behavioral rules agents should follow. The server also exposes [attachable study and report resources](/mcp-server/research-resources) for clients that show MCP resources in the conversation. These resources read the same authenticated public API as the research tools. ## Safety model The server advertises MCP safety annotations for every tool. Agents should also follow these product rules: 1. Use `customize_study` for the plan, audience, screeners, and concept material; do not reconstruct those fields in the MCP host. 2. Return the complete persisted study plan and obtain approval of its current version before creating BYOP participants, sharing an external-panel entry link, or launching paid Panel recruitment. 3. Use `estimate_panel`, show the complete estimate, and carry its `estimate_id` into an approved paid panel launch. 4. Require explicit user confirmation before rewards, webhooks, stopping fieldwork, or deleting studies, participants, or interviews. ## Runnable developer examples Use the [developer examples](/api-reference/developer-examples) to inspect study execution, report retrieval, and evidence search. The public repository includes fictional no-spend fixtures, a matching MCP/CLI walkthrough, and release compatibility notes. ## Agent homepage Start at [research.userintuition.ai](https://research.userintuition.ai/) for the three research workflows, connection options, machine-readable guidance, and public examples. This documentation remains the detailed operation reference. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.