AskOne: Live Q&A and Polls
Related Servers
Alternatives to AskOne: Live Q&A and Polls
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceLets an external AI agent work inside shared project rooms as a genuine client, handling seven tools that list and fetch projects, read full room state (project, document, recent chat, presence), post chat messages, edit the shared document, create projects, and upvote. Every action happens under a visible agent handle over the same REST and WebSocket endpoints humans use, returning schema-declared structured content and machine-readable error codes so agents can plan multi-step work.6 npmMIT- FlicenseNot gradedqualityBmaintenanceEnables AI agents to join ephemeral collaborative chatrooms, read room context, poll messages, publish findings, and update their status alongside human participants.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate a LiveKit deployment, managing rooms, tokens, participants, data messages, egress/ingress, and hackathon workshops with one-call room setup, status, broadcast, and teardown tools.MIT
- AlicenseAqualityDmaintenanceEnables MCP clients like Claude Code to read and post messages in a QRChat agent room without writing curl commands.30MIT

Bellmanofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-connected agent sessions across different providers and machines to collaborate in shared rooms, joining via relayable codes to preview and exchange briefs, messages, artifacts, action requests, and a shared read-only working surface. Also serves A2A-speaking agents through a public-room endpoint.834 npm4MIT
herdr-mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceEnables a chat or voice assistant to drive coding agents running in herdr: it can start an agent on a task, list and watch sessions started anywhere, send follow-ups, answer an agent's questions and approve or refuse its permission prompts. Long-running work is reported back through webhook callbacks so the conversation can continue without blocking.MIT
TDQS
Scored across 11 tools
Each tool has a distinct resource and action: rooms are listed/created/opened/closed, questions are read in two clearly differentiated formats (Markdown FAQ vs JSON with ids/paging), surveys are created/closed/results-read, and moderation/answering are separate operations. The two question-read tools could superficially overlap, but their descriptions explicitly state when to use each. No two tools appear to do the same thing.
All tool names use snake_case with a consistent verb_noun structure (list_rooms, get_room_qa, create_room, close_survey, moderate_question, etc.). Minor plural/singular variations (list_rooms vs create_room) are conventional and do not harm predictability. The pattern is clear and stable across the entire set.
The server exposes 11 tools, squarely within the ideal 3–15 range for a focused Q&A and polling service. Each tool corresponds to a meaningful operation in the room/question/survey lifecycle. There are no redundant or filler tools.
Core lifecycle coverage is strong: rooms can be created, opened, closed, and listed; questions can be read, moderated, and answered; surveys can be created, closed, and their results retrieved. Minor gaps exist, such as no direct get_room by code (list_rooms must be used), no survey update/delete, and no way to unanswer a question. These are workable limitations rather than critical missing operations.