Crowdhum MCP server
{
"mcpServers": {
"crowdhum": {
"type": "http",
"url": "https://mcp.crowdhum.com"
}
}
}{
"mcpServers": {
"crowdhum": {
"type": "http",
"url": "https://mcp.crowdhum.com"
}
}
}{
"mcpServers": {
"crowdhum": {
"type": "http",
"url": "https://mcp.crowdhum.com"
}
}
}{
"servers": {
"crowdhum": {
"type": "http",
"url": "https://mcp.crowdhum.com"
}
}
}{
"mcpServers": {
"crowdhum": {
"type": "http",
"url": "https://mcp.crowdhum.com"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.0
What it does
CrowdHum exposes live audience polling capabilities to AI assistants. Users can create polls from presentations or calendars, distribute scan-to-vote QR codes, view results in real time, and receive AI-generated recaps. Requires a CrowdHum Pro account with OAuth authentication.
- Create a multi-question poll from a presentation deck and share a QR code for live voting during a meeting.
- Run a word cloud or ranking poll during a standup or team session and get an AI summary of the results and themes.
- Generate poll suggestions based on upcoming calendar meetings or existing content, then retrieve and analyze live voting data.
Tools this server exposes
| Tool | Does |
|---|---|
| create_poll | Create a new poll with a specified visualization mode and options. |
| add_poll_to_session | Add a poll to an active session. |
| get_room_links | Retrieve QR code and room links for sharing a poll session. |
| get_poll_results | Fetch current voting results for a poll. |
| get_session | Retrieve details about a poll session. |
| get_session_recap | Get an AI-generated summary of a completed session. |
| list_my_sessions | List all sessions owned by the authenticated user. |
| list_my_polls | List all polls owned by the authenticated user. |
| list_visualizations | List available poll visualization modes. |
| invite_co_owner | Add a co-host to a poll session. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.