Hosted MCP server/Communication Official

Official AskOne: Live Q&A and Polls MCP server

Hosted at askone.org·Streamable HTTP

AskOne runs live audience Q&A and polls through an API token from askone.org. List existing rooms first; creating a room opens it immediately and consumes plan limits. A poll can then be added and launched, and questions approved, hidden, or marked answered. After the room closes, questions can be read as a FAQ draft and poll results retrieved. Free AI moderation is optional; the server uses HTTP and organization API key authentication.

askone.org Streamable HTTP OAuth or API key (Bearer) Source checked Nov 13, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Event hosts, community managers, and trainers who need live audience questions and polls without a separate moderation team.

  • List rooms in your organization (read-only).
  • Start an AskOne room for a live session, which opens it at once.
  • Add and launch a poll, then get results.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds AskOne: Live Q&A and Polls as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http askone-live-q-a-and-polls https://askone.org/api/mcp --header "Authorization: Bearer <ASKONE_API_TOKEN>" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer <ASKONE_API_TOKEN>
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://askone.org/api/mcp
Host
askone.org · /api/mcp
Transport
Streamable HTTP
Authentication
OAuth or API key (Bearer)
Server name
askone-live-q-a-and-polls
Listing type
Official provider listing

The installer uses the server name askone-live-q-a-and-polls. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that askone-live-q-a-and-polls appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List rooms in your organization (read-only). Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached askone.org when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 13, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

AskOne: Live Q&A and Polls documentationhttps://askone.org/docs/mcp