Integration

Survicate integration

Survicate is a customer feedback and survey platform (website, in-product, mobile, email and link surveys). This is its Data Export API, read-only for survey data: list surveys and read one with its author and attribute names, list a survey's questions, export a survey's responses with every answer (filtered by date range, with chosen respondent attributes), read one response, and list one respondent's attributes and responses across surveys. Two GDPR tools count, then permanently delete, everything held about one person. Responses carry respondents' answers and identifiers, which are personal data. Survey creation and editing, the response filters array and webhooks are not part of this integration. Authentication is the organization API key from Settings, Organization, Access Keys, sent as Authorization: Basic followed by the raw key; the plan must include the Data Export API.

Connect Survicate How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Survicate.Built from the 9 Survicate tools below, on the connection you add once.

What you can do with Survicate

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Response, 3 operations

get_survey_responseGet survey responseGETReturns one response to a survey (personal data) with every answer, device details, all its response-level attributes and the respondent's UUID.
list_respondent_responsesList respondent responsesGETLists every response one respondent gave across all surveys (personal data), newest first, each with the survey's id, type and name. Paged via the start in pagination_data.next_url.
list_survey_responsesList survey responsesGETLists a survey's responses (personal data), newest first, with every answer, device details and the respondent's UUID. Paged by time; for the next page pass the start found in pagination_data.next_url.

Personal data, 2 operations

delete_personal_dataDelete personal dataDELETEPermanently deletes all data held about one person (responses, respondent records, attributes, contacts, Insights Hub records), found by email, respondent UUID or user ID (send exactly one). Cannot be undone.
get_personal_data_countersGet personal data countersGETCounts the survey responses, respondent records and Insights Hub records held about one person, found by email, respondent UUID or user ID (send exactly one), to assess a GDPR request before deleting.

Survey, 2 operations

get_surveyGet surveyGETReturns one survey with its type, status, response count, launch schedule, author name and email, folder, first and last response times, and the names of the attributes sent with its responses.
list_surveysList surveysGETLists the surveys of the workspace, newest first, with their type, status, response count and launch schedule. Paged by creation date; for the next page pass the start found in pagination_data.next_url.

Attribute, 1 operation

list_respondent_attributesList respondent attributesGETLists every attribute of one respondent with its value (personal data), including attributes synced from integrations. Paged via the start in pagination_data.next_url.

Question, 1 operation

list_survey_questionsList survey questionsGETLists the questions of a survey with their type, text, introduction and answer choices (matrix questions also carry columns, contact forms their fields). Paged via the start in pagination_data.next_url.

Use Survicate from Claude Code, Cursor or Codex

Connect Survicate in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Survicate operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Survicate

Create your workspace
Sign up free. Nothing to install.
Connect Survicate once
Add your Survicate connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.