Connecting via MCP
The Attest MCP server lets you query your survey results conversationally from your AI assistant: no code, no exports, no pivot tables.
Use these details to connect any AI tool that supports MCP.
| Setting | Value |
|---|---|
| Server URL | https://mcp.askattest.com/mcp |
| Transport | Streamable HTTP |
| Sign-in | Sign in with your Attest account in Claude, ChatGPT and GitHub Copilot. Most other tools can sign in too. If yours can't, connect with an API key and let your account manager know which tool you use. Microsoft Copilot Studio uses an API key for now. Generate an API key. |
What you can do
Once connected, you can ask questions about your study results in natural language. Instead of exporting data and building pivot tables, you can interrogate your results directly.
"What studies do I have in Attest?"
"Show me the results from our Q1 brand tracker."
"What were the top reasons people gave for choosing a competitor brand?"
"How did awareness vary across age groups in the latest wave?"
"Has brand consideration changed since the previous wave?"
"Which segments showed the biggest shift in sentiment this quarter?"
"Give me a short summary of the key findings from this study that I can paste into a slide."
Available tools
Attest gives your AI assistant a set of tools, each for one kind of task.
| Tool | What it does |
|---|---|
| Search Studies | Finds your studies by name, status, owner, country or tag. Draft studies aren't included. |
| Get Study Structure | Gets a study's waves, audiences, questions and answer options. |
| Get Survey Responses | Gets results, either summarised by question or respondent by respondent, filtered by demographics or answers if you ask. |
| Get Demographics | Lists the demographic fields available in a market, so results can be filtered by them. |
| Get Segments | Lists a study's saved audience segments, such as "Gen Z", so they can be used as filters. |
| List Boards | Lists the boards built on a study's results. |
| Get Board | Opens a single board and its charts. |
| Get Key Findings | Gets the automatically generated key findings for a wave. |
What your AI assistant can see
- Only what your account can open. Your assistant acts as you. It can read the studies your own Attest account can open, and nothing else.
- Only published results. Draft studies aren't visible.
- Read-only. Your assistant can't create, change or delete anything in Attest.
- Respondent-level data when you ask for it. As well as summary results, your assistant can read individual respondents' answers, demographics and open-text responses.
Setup
Access is by approval. Connecting an AI tool to Attest only works for Attest accounts we've enabled. To get access, ask your Attest account manager.
Tip: Stuck on a step? Paste the error and ask your AI assistant for help troubleshooting.
Connect via Claude
Attest is listed in Claude's connector directory. You sign in with your Attest account, so there's no API key to copy and nothing to install. The connector works in Claude on the web, Claude desktop and the Claude mobile apps.
Step 1: Find Attest in the directory
- In Claude, open Customize in the left sidebar and select the Connectors tab. (You can also go to Settings → Connectors.)
- Click + or Add to browse the connector directory.
- Search for Attest.
You can also get there from a chat: click + in the bottom left of the message box, hover over Connectors and choose Manage connectors.
Claude is updating its menus, so the labels in your account may differ slightly from the steps here.
Step 2: Connect and sign in
- Click Connect.
- Sign in with your Attest account and approve access.
Attest now appears in your Connectors list as connected.
Step 3: Start asking
In a new chat, click +, hover over Connectors and check Attest is switched on. Then ask Claude about your studies, e.g. "What studies do I have in Attest?"
On a Claude Team or Enterprise plan? An owner of your Claude organisation needs to add Attest first, under Organization settings → Connectors → Browse connectors. After that, each person connects and signs in with their own Attest account.
Other ways to connect Claude desktop
If your organisation can't use the directory connector, you can still connect Claude desktop with an Attest API key.
Install the Attest desktop extension, or edit the config file
Option A: Install the extension
- Download the Attest extension (attest.mcpb).
- Double-click the downloaded file. Claude desktop opens and shows an install prompt for the Attest extension. You can also install it from within Claude: Settings → Extensions → Advanced settings → Install Extension…, then select the downloaded file.
- When prompted, paste in your Attest API key and click Install. Claude stores the key securely and does not display it again. Don't have an API key? Follow this guide to get one
- Make sure to Enable the Attest MCP.
- Once installed, Attest appears in Settings → Extensions as connected. You can ask Claude about your studies directly, with no restart needed.
Option B: Manual config
Step 1: Find your config file
Claude desktop reads its settings from a JSON config file on your computer. Open it in any text editor (e.g. TextEdit on Mac, Notepad on Windows).
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonTo open it quickly, press Cmd + Space, type Terminal, and run:
open -e ~/Library/"Application Support"/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonIf the file doesn't exist yet, create it. Open a text editor, paste in the config below, and save it at that path.
Step 2: Add the Attest server
Paste the following into the file, replacing YOUR_API_KEY with your Attest API key. Don't have an API key? Follow this guide to get one
{
"mcpServers": {
"attest": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://mcp.askattest.com/mcp",
"--header",
"X-API-Key: YOUR_API_KEY"
]
}
}
}If you already have other servers in the file, add the "attest" block inside the existing "mcpServers" object.
Requirements: Node.js must be installed on your computer. Download it here if needed.
Step 3: Restart Claude
Quit and reopen Claude desktop. Attest will appear as a connected tool. You can now ask Claude about your studies directly.
Connect via ChatGPT
Attest is listed in ChatGPT's plugin directory. You sign in with your Attest account, so there's no API key to copy.
Step 1: Find Attest in the plugin directory
In ChatGPT, select Plugins in the sidebar, or go to chatgpt.com/plugins. Search for Attest and open its listing.
Step 2: Install and sign in
- Click Install plugin.
- When prompted, click Connect and sign in with your Attest account.
Step 3: Start asking
In a new chat, type @ and choose Attest, then ask about your studies, e.g. "What studies do I have in Attest?"
On a ChatGPT Business, Enterprise or Edu workspace? Your workspace admin controls which plugins members can install. If you can't find or install Attest, ask them to make it available under Workspace settings → Plugins.
Connect via GitHub Copilot
Step 1: Find your config file
Where the config file lives depends on which GitHub Copilot you're using:
- VS Code:
.vscode/mcp.jsonin your workspace (or your user profile for a global setup). - CLI:
~/.copilot/mcp-config.json, or a.mcp.jsonfile in your project root.
If the file doesn't exist yet, create it.
Step 2: Add the Attest server
Add the following to your config file. Note that VS Code uses servers as the top-level key, while the CLI uses mcpServers.
VS Code (.vscode/mcp.json):
{
"servers": {
"attest": {
"type": "http",
"url": "https://mcp.askattest.com/mcp"
}
}
}CLI (~/.copilot/mcp-config.json or .mcp.json):
{
"mcpServers": {
"attest": {
"type": "http",
"url": "https://mcp.askattest.com/mcp"
}
}
}Step 3: Reload and sign in
- VS Code: reload the window, or run MCP: List Servers from the Command Palette.
- CLI: run
copilot mcp list.
On first use, a browser window opens asking you to sign in to Attest and approve access.
Connect via Microsoft Copilot
Sign-in with your Attest account is coming to Copilot Studio. Until then, connect with an API key.
Step 1: Open the MCP tool wizard
In Copilot Studio, open your agent and go to the Tools page. Select Add a tool → New tool → Model Context Protocol. This opens the MCP onboarding wizard.
Step 2: Add the Attest server
Fill in the server details:
- Server name:
Attest - Server description:
Provides access to Attest survey results and study data - Server URL:
https://mcp.askattest.com/mcp - Authentication:
- Select API key.
- Under Parameter type, select Header.
- In Header name, enter
X-API-Key. - In Key value, paste your Attest API key. Don’t have an API key? Follow this guide to get one.
Requirements: Copilot Studio supports the Streamable transport type for MCP servers. Attest's MCP server uses this transport, so no additional configuration is needed.
Step 3: Connect and add to agent
Select Create. In the Add tool dialog, create a new connection (or reuse an existing one), then select Add to agent. Attest will appear as a connected tool. You can now ask Copilot about your studies directly.
Connect via Gemini CLI
Step 1: Find your config file
Gemini CLI reads its settings from ~/.gemini/settings.json. Open it in any text editor.
To open it quickly on a Mac, run:
open -e ~/.gemini/settings.jsonOn Windows, run:
notepad %USERPROFILE%\.gemini\settings.jsonIf the file doesn't exist yet, create it and save it at that path.
Step 2: Add the Attest server
Paste the following into the file, replacing YOUR_API_KEY with your Attest API key. Don't have an API key? Follow this guide to get one
{
"mcpServers": {
"attest": {
"httpUrl": "https://mcp.askattest.com/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}If you already have other servers in the file, add the "attest" block inside the existing "mcpServers" object.
Step 3: Restart Gemini CLI
Close and reopen your terminal session, then run /mcp to check Attest is listed as connected. You can now ask Gemini about your studies directly.
Connect via other tools
- In your AI tool, find its option for adding a remote MCP server (often under integrations, connectors, or tools settings).
- Enter https://mcp.askattest.com/mcp as the server URL.
- Choose OAuth if the tool asks for an authentication method. Most tools detect this automatically, so you won’t need to enter an API key, header, or token.
- When prompted, a browser window opens asking you to sign in to Attest and approve read-only access.
- Once approved, you’re returned to your AI tool and Attest’s tools appear, ready to use.
If sign-in doesn't work, connect with an API key instead: add a header named
X-API-Key, with your Attest API key as its value. Don't have an API key? Follow this guide to get one. Then let your account manager know which tool you use, so we can add sign-in for it.
Getting the right level of detail
You don't need to change any settings to control how much your AI assistant pulls from Attest. Just ask in plain words, and it picks the right level of detail for you.
- Study outlines first. When you ask about a study, your assistant starts with a light outline: the questions, answer options and audiences. For more detail, such as screening questions, answers hidden from some audiences, or piped and randomised options, ask it to look at specific questions in full. "Show me Q3 in full."
- Open-text answers. Your assistant reads every verbatim answer by default. If you only want the gist, ask for a sample. "Give me a few examples of what people said."
- Raw exports come in pages. If you ask for raw, respondent-by-respondent answers, your assistant fetches a few respondents at a time and gets more as it needs them. Summary results always include every respondent.
- Finding studies. A study search shows up to 50 studies at a time. Searching by the study's name finds it faster. "Find my Q1 brand tracker."
- Whose studies are searched. By default, your assistant looks at studies you own. To include your colleagues' studies, just ask. "Search all studies in my team."
Turning off tools
You can block any tool you don't want your assistant to use and keep the rest. See Available tools for what each one does.
Your assistant needs Search Studies and Get Study Structure to find a study and its questions before it can read any results. If you block either one, it won't be able to answer most questions about your data.
- In Claude, open Customize in the left sidebar and select the Connectors tab, or go to Settings → Connectors.
- Select Attest.
- Under Tool permissions, each tool has three options:
- Always allow: Claude uses the tool without asking.
- Needs approval: Claude asks you before each use.
- Blocked: Claude can't use the tool.
- Choose an option for each tool you want to change. To change every tool at once, use the setting next to Read-only tools.
Changes apply straight away. Your other Attest tools keep working as normal.
On Claude Team and Enterprise plans, owners can set tool permissions for the whole organisation. If you can't change a setting, ask your Claude admin.
Using the Claude desktop extension?
If you connected with the Attest desktop extension instead of the directory connector:
- Go to Settings → Extensions.
- Next to Attest, click Configure.
- Scroll to Tool permissions and choose Always allow, Needs approval or Blocked for each tool, as above.
Workspace admins on ChatGPT Business, Enterprise and Edu can control which Attest actions are allowed:
- Go to Workspace settings → Plugins.
- Select Attest.
- On the plugin's page, review the included app's access and allowed actions.
Most AI tools let you turn off individual tools in their connector or MCP settings. Look for Attest in the same place you added it.
Troubleshooting
"Can't connect to Attest" or a sign-in error
Claude connector:
- In Claude, open Customize → Connectors (or Settings → Connectors) and select Attest.
- Disconnect it, then click Connect and sign in to Attest again.
- In your chat, click +, hover over Connectors and check Attest is switched on.
ChatGPT plugin:
- In ChatGPT, go to Plugins and open Attest.
- Disconnect your Attest account, then click Connect and sign in again.
- In your chat, type @ and check Attest is listed.
Claude desktop extension:
- In Claude desktop, go to Settings → Extensions and click Configure next to Attest.
- Check the extension is switched to Enabled. If it already is, switch it off and on again.
- Check your Attest API key is still valid in Attest under Settings. If it isn't, create a new one, paste it into the Attest API Key field and click Save.
Using a different AI tool? Remove Attest from its connector or MCP settings, add it again and sign in. If you connect with an API key (for example in Microsoft Copilot Studio), check the key is still valid.
I signed in, but my AI tool says I don't have access
Your Attest account needs to be enabled for MCP before the connector works. Ask your Attest account manager to request access for you.
My tool can't sign in to Attest
Sign-in works in most tools, but not all yet. Connect with an API key instead (see the Other tab under Setup), and let your account manager know which tool you use.
I can't find Attest in Claude's or ChatGPT's directory
Claude: On Team and Enterprise plans, an owner of your Claude organisation has to add Attest before members can connect it. Ask them to add it under Organization settings → Connectors. If your plan lets members request connectors, you can also click Request on Attest's page in the directory.
ChatGPT: On Business, Enterprise and Edu workspaces, an admin decides which plugins members can install. Ask them to make Attest available under Workspace settings → Plugins.
"Access denied" or a study is missing
Your AI assistant can only see studies your own Attest account can open. Check you can open the study in Attest. By default it only searches studies you own, so if a colleague ran the study, ask it to search your team's studies, e.g. "Search all studies in my team."
My assistant finds no results
Try naming the study more exactly, e.g. its full title. Also check the study is published, because drafts aren't visible to your assistant.
The response was too large or cut off
Ask for less at once, e.g. a summary instead of raw data, or a sample of open-text answers. See Getting the right level of detail.
My assistant says it can't use an Attest tool
The tool may be blocked in your settings. See Turning off tools to check and change it.
Still stuck?
Email [email protected]. Tell us which AI tool you're using and include any error message you see.
Updated about 4 hours ago