Skip to content

Connectors / Survey

Survey MCP connectors for Claude, ChatGPT and Cursor

5+ Survey connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

https://api.elaichi.ai/mcp The same for every user.
  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Survey connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

7 connectors

Browse all 400+ connectors →

In practice

What teams do with Survey connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Marketing

  • Check contact lists before a campaign

    Pull up every contact list in Alchemer, see which ones are in use, and confirm the right list exists before a survey invitation is scheduled.

  • Pull the profile assets for a campaign page

    Fetch your Trustpilot company profile, logo, header image, promotion box, and web links so a landing page shows the current star rating and the right artwork.

  • Turn highlight reels into customer stories

    List the highlight reels from recent tests, find the quotes where people describe the product in their own words, and reuse them for launch copy and case studies.

Operations

  • See every open action across your sites

    Ask for the actions still open at a particular location, of a particular type, or carrying a particular label, and get one list instead of clicking through each site in SafetyCulture.

  • Check who has filled in the intake form

    Ask how many responses the new vendor intake form has, and which submissions arrived since Monday. Chase the gaps instead of counting them by hand.

  • Audit the boards you actually have

    List every Canny board and spot duplicates or stale ones that should be merged or archived, then hand a tidy list to the product team.

Support

  • Reply to a product review conversation

    Open the conversation attached to a private product review, post a reply in your company's voice, and correct the wording later if you need to.

  • Match tickets to what testers already said

    When the same confusion keeps showing up in tickets, check whether UserTesting participants ran into it too, and hand the transcript to the product team as evidence.

  • Spot repeat complaints in satisfaction forms

    Ask which products or issues come up most often in the customer satisfaction form this month, and compare it to last month. Catch a pattern before it turns into a ticket backlog.

Product

  • See which product attributes draw complaints

    Pull attribute summaries across your product reviews to find out whether it is fit, battery life, or delivery that keeps getting mentioned, then take the list into planning.

  • Compare QX scores before a launch decision

    Pull the QX scores for every test on a feature and see whether the latest round of changes actually moved the numbers before you commit to a ship date.

  • Find the strongest quotes in user research

    Ask for the responses to the beta feedback form that mention a specific feature, and have the agent pull out the clearest quotes for the roadmap review.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Survey account you connected.

  • Summarize responses to the Q3 customer satisfaction survey.

    Alchemer

  • List every Canny board and its post count.

    Canny

  • Summarize this week's responses to the onboarding feedback form.

    Google Forms

  • List Prodege surveys live in Germany this week.

    Prodege

  • Which SafetyCulture actions are overdue this week?

    SafetyCulture

  • Summarize this week's product review sentiment by attribute.

    Trustpilot

  • Summarize last week's session results for the checkout study.

    UserTesting

The tools

What an agent can call in Survey

Connectors
5+

in the Survey catalog

Tools
576

callable the moment you connect

Hosted sign-in
6

connect with nothing to register

Of those 576 tools, 8% delete something. Restricting an agent to reads is not a promise here, it is 233 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 40%
233 tools · list, get, search
Write 20%
118 tools · create, update, send
Delete 8%
45 tools · delete, remove, archive
Other 31%
180 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Survey connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

Survey connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
SafetyCulture 363 Hosted
Alchemer 99 Hosted
Trustpilot 83 Your own app
UserTesting 13 Hosted
Prodege 11 Hosted
Google Forms 5 Hosted
Canny 2 Hosted

FAQ

Frequently asked questions

How many Survey connectors does Elaichi have?

5+ Survey connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Survey connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Survey account once makes it reachable from every one of them.

Do Survey connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Survey connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Survey connectors need me to bring my own OAuth app?

Most do not. 6 of the Survey connectors use Elaichi's hosted sign-in, with nothing to register. The other 1 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to Survey tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Survey connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Survey connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Put Survey connectors in front of your team

14 days on Gold, no credit card. Connect one and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.