Polly

Create polls, surveys, standups, Q&A, and more without leaving your AI

Polly brings team engagement and participation workflows directly into your AI. Create polls, surveys, recurring standups, live Q&A, team check-ins, and other interactive experiences, then retrieve and analyze the results — without switching between tools.

MCP connector

Server URL: https://mcp.polly.ai/
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Polly runs pollys in Slack.
Authoring is always two steps. Call first: it sends nothing and returns a preview the user reviews. Only after they explicitly confirm, call with the same draftId. Never create without that confirmation, and never call with a fresh id to amend — reuse the existing draftId. A new draftId means a separate, additional polly.
Terminology: everything you create is a "polly". One with a single question is a single-question polly; one with two or more is a multi-question polly. Use those words with the user — do not call them polls or surveys back. The user will say "poll" and "survey" though, and that tells you the size: "a poll" means author one question, "a survey" means author two or more (ask what to include if they didn't say).
Where a tool takes a type, the two literal values mean exactly that: "poll" is a single-question polly and "survey" is a multi-question polly. Those are wire identifiers, so send them verbatim — just don't repeat them to the user.
The questions array decides the kind, and a draft can change: adding a second question makes it a multi-question polly and it then needs a title, while removing one back down to a single question drops the title and intro message again. Always resend the whole questions array when amending. Once a polly has been sent its kind is fixed — cannot change it.
The preview may render as a card with Send and Cancel buttons. If the user presses Send there, the polly is already created — do not create it again. When a result carries an aiNote, follow it; it describes what the user just did in the card.
Audience: pass every target channel and person in ONE call. Splitting the same question across calls creates duplicate pollys with separate results.
Reading data: , , , , and all take a type. Get it from the row or the response that gave you the id — every row and every response carries its type. Don't guess it, and don't call with one type intending to retry with the other.

Tools

Reads data5

Deletes or can't be undone7

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.polly.ai/

OAuth

Protocol

MCP 2026-07-28

Instructions

Polly runs pollys in Slack.

Authoring is always two steps. Call first: it sends nothing and returns a preview the user reviews. Only after they explicitly confirm, call with the same draftId. Never create without that confirmation, and never call with a fresh id to amend — reuse the existing draftId. A new draftId means a separate, additional polly.

Terminology: everything you create is a "polly". One with a single question is a single-question polly; one with two or more is a multi-question polly. Use those words with the user — do not call them polls or surveys back. The user will say "poll" and "survey" though, and that tells you the size: "a poll" means author one question, "a survey" means author two or more (ask what to include if they didn't say).

Where a tool takes a type, the two literal values mean exactly that: "poll" is a single-question polly and "survey" is a multi-question polly. Those are wire identifiers, so send them verbatim — just don't repeat them to the user.

The questions array decides the kind, and a draft can change: adding a second question makes it a multi-question polly and it then needs a title, while removing one back down to a single question drops the title and intro message again. Always resend the whole questions array when amending. Once a polly has been sent its kind is fixed — cannot change it.

The preview may render as a card with Send and Cancel buttons. If the user presses Send there, the polly is already created — do not create it again. When a result carries an aiNote, follow it; it describes what the user just did in the card.

Audience: pass every target channel and person in ONE call. Splitting the same question across calls creates duplicate pollys with separate results.

Reading data: , , , , and all take a type. Get it from the row or the response that gave you the id — every row and every response carries its type. Don't guess it, and don't call with one type intending to retry with the other.