# Slido MCP connector

The Slido connector lets you pull audience questions, poll results, quiz and survey answers, participant lists and idea topics out of Slido events, rooms and spaces, so an AI assistant can request an export and report on it inside your own access.

Source: https://elaichi.ai/connectors/slido/

## Facts

| | |
| --- | --- |
| Application | Slido |
| Category | Event Management |
| AI tools | 17 |
| Authentication | App credentials |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Slido is connected

- Summarize the top questions from yesterday's all hands event.
- Which polls got the most votes last week?
- List participants who submitted idea topics in the product room.

## Connect Slido in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Slido.
2. Optionally set Share with, then press Connect.
3. Paste your Slido app credentials. Slido authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Slido tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Connect Slido to Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Connect Slido to ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Connect Slido to Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Slido to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Slido tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Slido through Elaichi

### Pull every audience question after the keynote

Events. Ask for an export of the questions and replies from this morning's room, then have the assistant group them by theme before the wrap-up meeting.

### Turn poll results into a follow-up email

Marketing. Request the poll and vote data from a webinar in Slido and get the top answers summarized in the language your attendees actually used.

### Summarize the all-hands Q&A for leadership

Internal communications. Export the questions, upvotes and idea topics from the town hall room and hand the CEO a one-page digest of what people asked about most.

### Check who actually took part in onboarding

People. Export the participant list from the new-hire session and compare it against the invite list to see who joined and who missed it.

### Score the quiz from the product training

Sales enablement. Pull the survey and quiz results from the enablement event and see which questions the sales team got wrong so the next session covers them.

### Collect feature requests from the community call

Product. Export the idea topics and questions raised during the customer meeting held over Webex and turn them into a tidy list for the roadmap review.

## Frequently asked questions

### How do I connect Slido to Claude?

Connect Slido in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Slido signs you in with app credentials from your Slido account, so there is no OAuth application to register and no client ID or secret to generate. Once that is done, Claude can request Slido exports as you.

### Does Slido work with ChatGPT and Cursor as well as Claude?

Yes. Slido is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You do not set Slido up again for each one.

### What can an AI agent actually do with my Slido data?

It can request an export from Slido of the things your events produce: audience questions and their replies, polls with their options and votes, quiz and survey answers, participant lists, idea topics, rooms, events, spaces and their users, and meetings held over Webex. It can then check on a specific export or list the ones already requested, and read the results back to you. It does not run your live event or change what attendees see.

### Does connecting Slido give the AI access to every event and space?

No. Every request to Slido runs as the person who signed in, so the AI only reaches the Slido events, rooms and spaces that person can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Slido itself grants.

### Can my team share one Slido connection?

Yes. One person connects Slido in Elaichi and shares the connection with a team, and nobody else ever handles the Slido app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the real person behind every Slido export.

### Can I stop an agent from deleting or changing things in Slido?

This Slido connector only requests exports and reads them back, so it does not edit polls, questions or events. Even so, restrictions in Elaichi work per action, so you can block requesting particular kinds of Slido exports, such as participant lists. A blocked action is never shown to Claude, ChatGPT or Cursor, so no prompt can reach it.

### What happens to a Slido connection when someone leaves?

Offboarding that person in Elaichi ends their access to Slido through every AI client at once. If they had shared a Slido connection with a team, it keeps working for everyone else. Disconnecting Slido once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

## All 17 Slido tools

Every tool below is callable through https://api.elaichi.ai/mcp once Slido is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Slido exports user** (Create). Start an asynchronous export of users in Slido. Returns a 202 export job object that can be polled for completion. The exported user records include user_id, display_name, email, role, is_active, created_date, joined_date, and modified_date.
- **Create a Slido exports event** (Create). Start an asynchronous export of events in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported event records include event_id, owner_user_id, start_date, end_date, timezone, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all events).
- **Create a Slido exports room** (Create). Start an asynchronous export of rooms in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported room records include room_id, event_id, event_owner_user_id, is_active, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all rooms).
- **Create a Slido exports participant** (Create). Start an asynchronous export of participants in Slido. Returns an export job object (HTTP 202) for polling export status. The exported participant data includes event_owner_user_id, event_id, participant_id, name, email, user_id, first_joined_date, and modified_date. Accepts an optional participants filter in the request body.
- **Create a Slido exports question** (Create). Start an asynchronous export of Q&A questions in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported question records include question_id, event_owner_user_id, event_id, room_id, participant_id, status, is_anonymous, is_starred, score, upvotes, downvotes, highlighted_date, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all questions).
- **Create a Slido exports question reply** (Create). Start an async export of question replies in Slido. Returns: id, type, status, result. The exported data includes question_reply_id, event_id, room_id, question_id, text, status, is_anonymous, is_private, is_pinned, posted_by_moderator, participant_id, created_date, and modified_date per reply.
- **Create a Slido exports surveys quizz** (Create). Start an asynchronous export of surveys and quizzes in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported records include survey_quiz_id, event_owner_user_id, event_id, room_id, type, polls_count, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all surveys/quizzes).
- **Create a Slido exports poll** (Create). Start an async export of polls in Slido. Returns: id, type, status, result. Accepted asynchronously (202); use the Get Export endpoint to retrieve the export result.
- **Create a Slido exports poll option** (Create). Start an asynchronous export of poll options in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported poll option records include poll_option_id, event_owner_user_id, event_id, room_id, survey_quiz_id, poll_id, is_correct, order, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all poll options).
- **Create a Slido exports poll vote** (Create). Start an asynchronous poll votes export in Slido. Returns an export job object (202 Accepted) with an export_id for polling status and download URL via the Get Export endpoint. The exported data includes poll_vote_id, event_id, room_id, poll_id, participant_id, is_anonymous, created_date, and modified_date for each poll vote.
- **Create a Slido exports poll vote value** (Create). Start an asynchronous export of individual poll vote values (answer selections) in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported records include poll_vote_value_id, event_owner_user_id, event_id, room_id, survey_quiz_id, poll_id, poll_vote_id, participant_id, is_anonymous, rating_score, multiple_choice_option_id, quiz_option_id, ranking_option_id, ranking_rank, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all poll vote values).
- **Create a Slido exports idea topic** (Create). Start an async export of idea topics in Slido (deprecated — works with the retired Ideas BETA feature; use polls endpoints for the new Ideas poll). Returns: id, type, status, result. The request body accepts an optional filter object that defaults to empty.
- **Create a Slido exports webex meeting** (Create). Start an export of Webex meetings in Slido. Returns: id, type, status, result, export_id. The exported data includes event_id, event_owner_user_id, webex_meeting_id, and modified_date. The export is processed asynchronously.
- **Create a Slido exports space** (Create). Start an async Slido spaces export. Returns the export record including space_id, organization_id, name, description, type, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty).
- **Create a Slido exports spaces user** (Create). Start an export of Spaces users in Slido. Returns a 202 Accepted response with an ExportOut object for tracking the async export job. The exported data includes space_id, organization_id, user_id, created_date, and modified_date.
- **Get single Slido export by ID** (Get). Get details of a specific export in Slido by its export id. Returns the export object including its export_id, type, and status. Required: id.
- **List all Slido exports** (List). List all Slido exports. Returns a list of export objects including export_id and type. Optional: type to filter exports by export type.