Skip to main content
You don’t call these tools yourself — your AI assistant picks the right ones based on what you ask. This page is a reference for what’s possible and what permissions each capability needs.

Permission scopes

The consent screen shows exactly which scopes will be granted when you connect. Every client covered in the setup guide receives all three scopes, including connectors with no configurable scope field. If you’re building your own client, you can request a read-only connection by sending an explicit scope with just the read scopes. Scopes are fixed when a client connects. To change them (for example, to add write access to a connection that was approved read-only), disconnect the client and connect it again so the consent screen runs with the new scopes. Scopes are an upper bound, not a bypass: every request is also checked against your organization role and each study’s access policy, so an agent can never see or change more than you can in the dashboard.

Tools

Studies

Questions

Question groups

Randomizers

Randomizers are weighted split tests: each participant is routed to exactly one arm, and an arm shows one question or one question group (or is left empty as a placeholder while you build). Use a randomized question group when you only want to shuffle order.

Logic rules

Interviews & results

Capabilities

Help center

Prompts

Prompts are ready-made analysis workflows. Most clients surface them in a prompt or command menu (in Claude, look under the connector’s entry in the tools menu).

Resources

Good to know

Your agent handles fetching and pagination on its own — there’s nothing to configure. A few things to know:
  • Question media links expire. get_question_details returns each asset’s stable url plus a usable download_url. Private download links last one hour, with their UTC expiry in download_url_expires_at. Fetch details again to refresh a link. A null download URL means the private file is currently unavailable.
  • Numbers can differ from a casual dashboard glance. Mock and archived interviews are never exposed over MCP, and simulated interviews are always reported separately from real ones — so MCP counts reflect real research activity only.
  • A few things still happen in the dashboard. Figma prototype tasks, tree tests, and conjoint questions are configured there (their text stays editable via MCP), and stimulus media is attached there. Agents check the get_capabilities tool for the full list of unsupported features, each with a workaround, so they’ll route around these on their own.