Create the right study
Turn a research question into a card sort, tree test, survey, first-click, first-impression, prototype, or live website study.
Veritio MCP is live
Your AI assistant, now fluent in your research.
Connect Veritio to the AI tools you already use. Create studies, inspect evidence, work with participants, and move findings forward without rebuilding context in every conversation.
- Hosted remote server
- OAuth setup
- Full or read-only
You
Build a tree test from this sitemap and check it before launch.
study_createTree test created
Donestudy_content_set24 tree nodes added
Donestudy_validateReady for your review
ReadyThe study is configured and passes its readiness checks. I have not launched it.
Connect from the tools already in your workflow
- Codex
- Claude Code
- Cursor
- VS Code
One research surface
Go from question to evidence in the same conversation.
Veritio exposes the real research workflow, not a read-only document search, while keeping every action behind scopes and resource-level permissions.
Configure the details
Add tasks, questions, cards, tree nodes, study flow, and settings without leaving the conversation.
Validate before launch
Check readiness, see exactly what is missing, and launch only after the study is ready and you approve it.
Interrogate the evidence
Ask for task metrics, participant responses, patterns, and concise result summaries in the same workspace as your analysis.
Work with participants
Find panel members, inspect segments and tags, and keep recruitment context close to the study it supports.
Move findings forward
Manage study sharing, generate insights, create exports, and collaborate through comments, tags, recordings, and clips.
Three steps
Connect once. Keep the research context.
The recommended remote connection uses the MCP standard and opens Veritio in your browser for authentication. There is no local server to maintain and no API key to paste into an interactive client.
Add Veritio
Choose Codex, Claude Code, Cursor, or VS Code and install the secure remote endpoint.
Approve access
Sign in to the right workspace, choose full or read-only access, and review the requested scopes.
Ask naturally
Work with studies and evidence from the conversation while Veritio enforces your existing permissions.
Open guided setup Usually takes a minute. No API key required.
Try asking
Prompts that end in real research work.
MCP lets the assistant move beyond advice. It can use authorized Veritio tools, show you what happened, and stop for review before consequential actions.
“Create a tree test from this sitemap, add the three navigation tasks, and tell me what is still required before launch.”
A configured study with an explicit readiness check.
“Compare task success and time-on-task across this first-click study. Summarize the strongest usability signal.”
Evidence-backed findings without exporting raw rows first.
“Find panel participants tagged enterprise and mobile, then show me the matching segments before I make any changes.”
A permission-aware shortlist you can review in context.
“Generate concise insights for this study and prepare an export I can share with the product team.”
A faster path from completed study to usable evidence.
Designed for controlled access
Useful to your assistant. Still accountable to you.
Remote access should be easier without becoming invisible. Veritio keeps authentication, consent, scopes, and workspace roles in the path of every request.
OAuth, not copied secrets
Interactive clients open Veritio in your browser. Sign in once, review the requested access, and return to your AI tool.
A hard read-only option
Choose the read-only endpoint when the assistant should analyze research without exposing any mutating tools.
Workspace roles still apply
A granted scope never overrides your role. Every call checks the relevant organization, project, study, or participant resource.
Revocable, scoped access
Veritio uses OAuth 2.1 with PKCE, short-lived access, rotating refresh tokens, and explicit research scopes.
Need analysis without mutations?
Choose read-only setup The dedicated read-only endpoint never advertises create, update, launch, participant-write, sharing, or export tools.
Questions
Before you connect
The setup page includes exact instructions for each supported client. These are the important product and access details.
What is an MCP server?
The Model Context Protocol is a standard way for AI assistants to use tools and approved data from another product. Veritio MCP makes research capabilities available through that shared interface instead of a custom integration for every AI client.
Do I need to create an API key?
Not for normal interactive use. Codex, Claude Code, Cursor, and VS Code can connect through browser-based OAuth. Scoped API keys remain available for CI, headless automation, self-hosted environments, or older clients that cannot complete OAuth.
Can my AI assistant change research data?
Only if you choose standard access and approve write scopes. Read-only mode removes mutating tools at the server boundary. Irreversible actions such as launching a study also run readiness checks and require explicit confirmation.
Does MCP bypass Veritio permissions?
No. Scopes control the kind of action a credential may attempt, while Veritio separately checks the signed-in user’s role on the exact workspace, project, study, or panel resource involved in each call.
Where does the MCP server run?
The recommended endpoint is hosted by Veritio over secure Streamable HTTP, so there is no local server to keep running. A published stdio bridge is available as a compatibility option for clients that cannot connect to a remote server directly.
Veritio MCP
Put your research where the work is happening.
Connect your preferred AI client, approve the access you want, and start with a real study or result.
OAuth setup. No API key required. Revoke access any time.