Skip to content

Connectors / Survey

Survey MCP connectors for Claude, ChatGPT and Cursor

10+ 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.

13 connectors

Browse all 600+ 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.

  • Import a customer list for a survey

    Hand over a list of customers and have them imported into Rally as people, then added to the right study ready for the screener.

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.

  • Pull this week's inspections with a query

    Run a Fulcrum query for inspections completed since Monday and get the results back as a plain list, grouped by site or status.

  • Catch up on today's field submissions

    Ask which DataScope forms came in from each site this morning and get the answers summarized before the standup, without opening every PDF.

Support

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

  • Read customer feedback without opening Fillout

    Pull the latest responses to your feedback survey and ask what customers keep mentioning. Every submission stays tied to the form it came from.

  • Find the complaint form submissions from today

    Pull the day's submissions to the issue report form and sort them by product so the desk knows where to start.

Product

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

  • See every feedback board at a glance

    Ask for a rundown of all your Canny boards before a roadmap review, so you know which feature request, bug, and idea boards are live without opening Canny.

  • Hear what beta testers said this week

    Ask for a rundown of the latest submissions to the feedback form and get the recurring requests and complaints grouped, without opening the results tab.

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 yesterday's safety checklist answers by location

    DataScope

  • Show me yesterday's submissions to the customer feedback form.

    Fillout

  • Which Fulcrum forms were created this month?

    Fulcrum

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

    Google Forms

  • Summarize this week's submissions to the customer feedback form

    Jotform

  • List Prodege surveys live in Germany this week.

    Prodege

The tools

What an agent can call in Survey

Connectors
10+

in the Survey catalog

Tools
841

callable the moment you connect

Hosted sign-in
4

connect with nothing to register

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

Read 39%
330 tools · list, get, search
Write 20%
168 tools · create, update, send
Delete 6%
50 tools · delete, remove, archive
Other 35%
293 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. API key and App credentials mean an admin pastes them once, with nothing to register.

Survey connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
SafetyCulture 363 API key
Fulcrum 144 API key
Alchemer 99 API key
Trustpilot 83 Your own app
Rally 68 Hosted
DataScope 38 API key
UserTesting 13 App credentials
Prodege 11 API key
Fillout 8 API key
Jotform 7 Hosted
Google Forms 5 Hosted
Canny 2 API key
Tally Hosted

FAQ

Frequently asked questions

How many Survey connectors does Elaichi have?

10+ 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 or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. 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. 4 of the Survey connectors use Elaichi's hosted sign-in, with nothing to register. 8 connect with an API key or app credentials that an admin pastes once, with no app to register. 1 asks 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 left out of the model's tool list and cannot be called. 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.