ReactLive
com.reactlivePublished by reactlive.comOfficial publisherv1.0.1Updated Oct 24, 2026
Live audience engagement: run Q&A, polls, liveblogs and chat for webinars and town halls.
Overview
ReactLive is a remote MCP server for running live audience engagement such as Q&A, polls, liveblogs and chat during webinars and town halls.
- What you can do
- Run live Q&A sessions for webinars and town halls, letting an assistant work with audience questions and responses through the connected ReactLive account. Collect audience input through polls and surface the results. Manage liveblog and chat activity so an assistant can help follow and organize the conversation as it happens. The manifest lists no individual tools, so the exact operations available depend on what the ReactLive connector exposes.
- When to use it
- Useful when you host webinars, town halls or other live events on ReactLive and want an assistant to help manage audience questions, polls, liveblogs or chat during the session.
- Requirements
- A remote server reached at the ReactLive endpoint over streamable HTTP. Authentication is required via OAuth, so you need a ReactLive account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open ReactLive in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.reactlive%2Freactlive/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"reactlive": {
"type": "http",
"url": "https://www.reactlive.com/api/v2/mcp"
}
}
}Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.