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 a client requested when you connect. Read scopes are granted by default; write access must be explicitly requested by the client. 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

Logic rules

Interviews & results

Capabilities

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. Two things are worth knowing so results make sense:
  • 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.