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.
MCP integration uses the same API key as the REST API. Generate an API key first before continuing.
Setup
Tip: Stuck on a step? Paste the error and ask your AI assistant for help troubleshooting.
Connect via Claude Desktop
The fastest way to connect is with the Attest extension file (.mcpb) — no config editing and no Node.js install required. If you'd rather edit the config file directly (or the extension isn't available on your setup), use the manual method below.
Option A — Install the extension (recommended)
- 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, 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 Microsoft Copilot
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, then enter 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 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",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}CLI (~/.copilot/mcp-config.json or .mcp.json):
{
"mcpServers": {
"attest": {
"type": "http",
"url": "https://mcp.askattest.com/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with your Attest API key.
Don't have an API key? Follow this guide to get one
Step 3 — Reload and verify
- VS Code: Reload the window, or run MCP: List Servers from the Command Palette to confirm Attest shows up and is running.
- CLI: Run
copilot mcp listto confirm Attest is reported as connected.
Note: In VS Code, if you're a member of an organization on a Copilot Business or Enterprise plan, the "MCP servers in Copilot" policy must be enabled for MCP to work at all.
Step 1 — Turn on developer mode
Go to Settings → Connectors and enable Developer mode.
Step 2 — Start adding a connector
Still in Settings → Connectors, click +.
Step 3 — Add the Attest server
Enter the server URL:
https://mcp.askattest.com/mcpStep 4 — Authenticate
When prompted, enter your Attest API key. Don't have an API key? Follow this guide to get one
Step 5 — Save
Click Save. Attest will appear as a connected tool.
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, run:
open -e ~/.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": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://mcp.askattest.com/mcp"
],
"env": {
"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 Gemini CLI
Close and reopen your terminal session. Attest will appear as a connected tool and you can now ask Gemini about your studies directly.
Connect via ChatGPT
Step 1 - Turn on developer mode
Go to Settings → Connectors and enable Developer mode. This unlocks the option to add a custom MCP connector.
Step 2 - Start adding a connector
Still in Settings → Connectors, click +.
Step 3 - Add the Attest server
Enter the server URL:
https://mcp.askattest.com/mcpStep 4 - Authenticate
When prompted, enter your Attest API key. Don't have an API key? Follow this guide to get one.
Step 5 - Save
Click Save. Attest will appear as a connected tool, and you can now ask ChatGPT 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.
- Find where it asks for an API key or auth token, and paste your API key there. This is usually a header or an environment variable, depending on the tool.
- Once approved, Attest's tools appear in that AI tool, ready to use.
What the MCP unlocks
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."
Updated 5 days ago