MCP is an open standard, so Survio works with more tools than we can write guides for - VS Code and GitHub Copilot, Windsurf, Zed, Warp, n8n, and new ones arriving all the time.
They all need the same two things, and there's nothing to generate in Survio beforehand.
What every tool needs
Server URL |
|
Transport | HTTP, sometimes labelled "Streamable HTTP", "Remote" or "HTTP/SSE" |
Authentication | OAuth - you sign in with your Survio account, with no key or token to paste |
How to add the server
Step 1 - Open your tool's MCP settings
Look for MCP, MCP Servers, Integrations, Connectors or Tools - usually in settings, or in the command palette.
Step 2 - Add a remote HTTP server
Not a local, stdio or command-based one. Those run as a program on your own computer; Survio's runs on our side.
Name:
Survio, orsurvioif your tool wants lowercase without spacesURL:
https://ai.survio.com/mcp
Leave any API key, token or header fields empty.
Step 3 - Authorize
Sign in with your Survio account when your browser opens. Some tools make this a separate step - look for Connect, Log in or Authenticate next to the server.
Step 4 - Try it
List my Survio surveys.
If your tool only accepts a config file
The shape is near-identical across tools:
{
"mcpServers": {
"survio": {
"type": "http",
"url": "https://ai.survio.com/mcp"
}
}
}Two differences to watch for: some tools use servers instead of mcpServers (VS Code, for example), and a few omit "type" and infer it from "url". Check your tool's documentation for the key names - the URL is the same either way.
If the file already has servers, add "survio" inside the existing object, then restart the tool.
If your tool doesn't support remote servers
Some only support local stdio servers. You can still connect through the mcp-remote bridge, which needs Node.js:
{
"mcpServers": {
"survio": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ai.survio.com/mcp"]
}
}
}
