Testable MCP connector
Testable MCP is a connector between your Testable account and an AI assistant, such as Claude or ChatGPT. MCP means Model Context Protocol, a standard that lets an AI assistant use other services. With the connector, you can ask your assistant to build a project, edit a trial file or summarize your results, and the assistant does the work in your Testable account.
This page explains how to connect, lists the tools, and gives the technical details behind the section on AI assistants in our Privacy Policy.
Connect
Section titled “Connect”Step-by-step instructions for ChatGPT, Claude, Grok and coding agents are in Testable MCP. In short:
- In your AI assistant, add a custom connector (some assistants call it a custom MCP server).
- Enter the server URL:
https://www.testable.org/mcp - The assistant opens Testable. Sign in with your Testable account and select Connect.
The sign-in uses OAuth, a standard that gives the assistant access without your password. Your assistant never sees your Testable password.
To check the connection, ask: “Which Testable account am I connected to?”
Example prompts
Section titled “Example prompts”- “List my Testable projects.”
- “Create a new project with a Stroop task that has 20 practice trials.”
- “Show me the trial file of my project and explain what each column does.”
- “How many participants completed my study, and how many dropped out?”
- “What is the mean reaction time per condition in my project?”
- “How much budget do I have left on Testable Minds?”
What the assistant can read and change
Section titled “What the assistant can read and change”The assistant acts as you. It can see only the projects that you own or collaborate on. Results of a project that you collaborate on are available only if its owner shares results with collaborators.
Your assistant decides when to call a tool. Check its settings to make it ask you before it acts.
| Group | The assistant can read | The assistant can change |
|---|---|---|
| Account | Your login, name and email address | Nothing |
| Projects | Project list, project settings, trial files, the list of stimulus files, the trial column documentation | Create, copy and import projects. Replace or edit the trial file. Upload, overwrite and delete stimulus files. Change project settings. |
| Results | Participant runs, trial responses, summaries, statistics, read-only queries and exports | Nothing |
| Library | Nothing extra | Publish one of your projects to the public Testable library, or update an entry you published |
| Testable Minds | Your budget, studies, sessions and respondents | Nothing |
Some changes to a live project that already has results are refused until the assistant confirms the change explicitly.
Participant data in results
Section titled “Participant data in results”Results tools can return these categories of data for each participant run:
- Trial responses, as recorded by your experiment.
- Demographics that the participant provided: age, gender, sex assigned at birth, education, handedness, sexual orientation, ethnicity, nationality, and your custom demographic fields.
- Participant identifiers: the Testable Minds code and the participant id from an external recruitment service.
- Device details, such as browser, operating system, screen size and frame rate.
- Timestamps of the run.
- Status flags, such as whether the participant gave consent.
For Testable Minds respondents, the assistant can read the Minds code, status, age, sex, location, browser, device type, screen resolution, start time, completion time and payment (reward and bonus). The respondent’s name is included only if the session is set to show names.
The summary and statistics tools return totals and averages. Use them when you do not need the data of single participants.
Fields that are withheld
Section titled “Fields that are withheld”These fields are never returned to the assistant, also not in queries and exports:
- Participant IP addresses.
- Browser session ids.
- Completion codes.
The connector has 26 tools. Each tool tells the assistant what kind of access it needs:
- Read only. The tool never changes your data.
- Adds. The tool creates a new project and does not change existing ones.
- Changes. The tool can overwrite or delete content in an existing project.
- Publishes. The tool makes a project public.
Many assistants use these labels to ask you before a tool changes something.
Account
Section titled “Account”| Tool | What it does | Access |
|---|---|---|
whoami | Shows the login, name and email address of the connected account. | Read only |
Projects and trial files
Section titled “Projects and trial files”| Tool | What it does | Access |
|---|---|---|
list_projects | Lists the projects that you own or collaborate on. | Read only |
get_project | Shows the settings of one project and a preview of its trial file. | Read only |
get_trial_file | Returns the trial file of a project. | Read only |
list_stimuli | Lists the stimulus files of a project. | Read only |
list_trial_columns | Lists the trial file columns by category, with a short description of each. | Read only |
get_trial_column_docs | Returns the full documentation of a trial file column or category. | Read only |
create_project | Creates a new project. | Adds |
copy_project | Copies one of your projects into a new project. Results are not copied. | Adds |
import_library_project | Copies a test from the Testable library into a new project in your account. | Adds |
update_project_settings | Changes the settings of a project. | Changes |
set_trial_file | Replaces the full trial file of a project. | Changes |
edit_trials | Inserts, updates or deletes rows in a trial file. | Changes |
put_stimulus | Uploads a stimulus file, or overwrites a file with the same name. | Changes |
delete_stimulus | Deletes a stimulus file. | Changes |
Results
Section titled “Results”| Tool | What it does | Access |
|---|---|---|
get_results_summary | Shows the number of runs, the completion funnel and statistics per subject group. | Read only |
list_results | Lists the participant runs of a project. | Read only |
get_result | Returns the trial responses of one participant run. | Read only |
get_results_stats | Returns the statistics from the results dashboard of a project. | Read only |
query_results | Runs a read-only SQL query (DuckDB) on the trial responses of a project. | Read only |
export_results | Exports results as CSV: one row per participant, one row per trial response, or the participants who did not finish. | Read only |
Library
Section titled “Library”| Tool | What it does | Access |
|---|---|---|
share_to_library | Publishes one of your projects to the public Testable library, or updates an entry that you published. | Publishes |
Testable Minds
Section titled “Testable Minds”| Tool | What it does | Access |
|---|---|---|
list_studies | Lists your Minds studies. | Read only |
get_study | Shows the settings, screening criteria and sessions of one study. | Read only |
list_respondents | Lists the respondents of one session, with status, demographics, timing and payment. | Read only |
get_minds_budget | Shows your Minds balance and the amount held for running sessions. | Read only |
Exports
Section titled “Exports”When an export is too large to return directly, or the assistant asks for a file, Testable stores the file on its servers and gives the assistant a download link.
- The link works for 15 minutes.
- The link works without signing in. Anyone who has the link can download the file in that time.
- An hourly job deletes the file after the link has expired.
How long access lasts
Section titled “How long access lasts”- Access tokens. A token is a digital key that lets the app act for your account. An access token expires after one hour.
- Refresh tokens. The app uses a refresh token to get a new access token without asking you to sign in again. A refresh token expires after 30 days. An app that you use regularly stays connected.
- Static tokens. For tools that cannot use the OAuth sign-in, you can create a static token under Account, then Testable MCP. A static token expires after 90 days.
What Testable records
Section titled “What Testable records”- Tool inputs. Testable receives what the assistant sends to a tool, such as a project id, a trial file or a query. Content that a tool saves, such as a trial file or a stimulus file, is stored in your project like content that you add yourself.
- Conversations. Testable does not receive or store your conversations with the assistant.
- Connection records. The name of each connected app, when it connected, when it was last used, and identifiers of its tokens.
- Request log. For each request: your login and account id, the connected app, the type of sign-in, the tool name, the project id, the outcome and the time, plus technical protocol data such as the status code. The log does not contain tool inputs or results.
- Web server logs. Like every request to Testable, a connector request is recorded with technical data such as your IP address.
- Error reports. When an error occurs, technical details go to our error monitoring provider (see the list of sub-processors). A report can include your IP address and account id. Testable removes tool inputs, access tokens and cookies from these reports. An error message can still contain a part of an input.
Retention periods are in the Privacy Policy.
Where the data goes
Section titled “Where the data goes”Data that a tool returns goes to the AI provider that you connected. From then on, the terms and privacy policy of that provider apply. Review the data settings of your provider before you connect, for example whether it uses your chats to train its models.
For participant data, you remain the data controller. Before you share participant-level results with an AI assistant, check that your consent form, information sheet and ethics approval allow it. See Processing of Data.
Disconnect
Section titled “Disconnect”- Go to Account, then Testable MCP.
- Select Disconnect next to the app, or revoke the static token.
The app loses access at once. You can also remove the connector in the settings of your AI assistant, but only the Testable page ends the access on our side.
To ask for a copy of the data that Testable keeps about your connections, or for its deletion, write to contact@testable.org.