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.

SettingValue
Server URLhttps://mcp.askattest.com/mcp
TransportStreamable HTTP
Sign-inSign 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.

Find a study and explore results

"What studies do I have in Attest?"

"Show me the results from our Q1 brand tracker."

Dig into specific questions

"What were the top reasons people gave for choosing a competitor brand?"

"How did awareness vary across age groups in the latest wave?"

Track changes over time

"Has brand consideration changed since the previous wave?"

"Which segments showed the biggest shift in sentiment this quarter?"

Summarise and share

"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.

ToolWhat it does
Search StudiesFinds your studies by name, status, owner, country or tag. Draft studies aren't included.
Get Study StructureGets a study's waves, audiences, questions and answer options.
Get Survey ResponsesGets results, either summarised by question or respondent by respondent, filtered by demographics or answers if you ask.
Get DemographicsLists the demographic fields available in a market, so results can be filtered by them.
Get SegmentsLists a study's saved audience segments, such as "Gen Z", so they can be used as filters.
List BoardsLists the boards built on a study's results.
Get BoardOpens a single board and its charts.
Get Key FindingsGets 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

  1. In Claude, open Customize in the left sidebar and select the Connectors tab. (You can also go to Settings → Connectors.)
  2. Click + or Add to browse the connector directory.
  3. 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

  1. Click Connect.
  2. 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

  1. Download the Attest extension (attest.mcpb).
  2. 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.
  3. 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
  4. Make sure to Enable the Attest MCP.
  5. 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.json

To open it quickly, press Cmd + Space, type Terminal, and run:

open -e ~/Library/"Application Support"/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

If 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.


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.

  1. In Claude, open Customize in the left sidebar and select the Connectors tab, or go to Settings → Connectors.
  2. Select Attest.
  3. 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.
  4. 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:

  1. Go to Settings → Extensions.
  2. Next to Attest, click Configure.
  3. Scroll to Tool permissions and choose Always allow, Needs approval or Blocked for each tool, as above.

Troubleshooting

"Can't connect to Attest" or a sign-in error

Claude connector:

  1. In Claude, open Customize → Connectors (or Settings → Connectors) and select Attest.
  2. Disconnect it, then click Connect and sign in to Attest again.
  3. In your chat, click +, hover over Connectors and check Attest is switched on.

ChatGPT plugin:

  1. In ChatGPT, go to Plugins and open Attest.
  2. Disconnect your Attest account, then click Connect and sign in again.
  3. In your chat, type @ and check Attest is listed.

Claude desktop extension:

  1. In Claude desktop, go to Settings → Extensions and click Configure next to Attest.
  2. Check the extension is switched to Enabled. If it already is, switch it off and on again.
  3. 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.


Did this page help you?