Livestorm

Manage Livestorm webinars, sessions and registrants.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Livestorm connector does

The Livestorm MCP server connects a Livestorm webinar workspace to Claude, ChatGPT and any MCP-compatible agent. Its 41 tools map one-to-one onto Livestorm's Public API v1, covering events, sessions, registrants, chat transcripts, team members and webhooks. Sign-in is OAuth 2.1 with dynamic client registration, and the grant offers two scopes.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Livestorm tools (41)

  • livestorm_assign_tag
  • livestorm_bulk_register_people
  • livestorm_create_event
  • livestorm_create_event_session
  • livestorm_create_user
  • livestorm_create_webhook
  • livestorm_delete_event
  • livestorm_delete_session
  • livestorm_delete_user
  • livestorm_delete_webhook
  • livestorm_get_current_user
  • livestorm_get_event
  • livestorm_get_event_person
  • livestorm_get_job
  • livestorm_get_organization
  • livestorm_get_person
  • livestorm_get_session
  • livestorm_get_session_person
  • livestorm_list_chat_messages
  • livestorm_list_event_people
  • livestorm_list_event_sessions
  • livestorm_list_events
  • livestorm_list_job_tasks
  • livestorm_list_people
  • livestorm_list_people_attributes
  • livestorm_list_questions
  • livestorm_list_recordings
  • livestorm_list_session_people
  • livestorm_list_sessions
  • livestorm_list_team_members
  • livestorm_list_webhooks
  • livestorm_patch_event
  • livestorm_patch_session
  • livestorm_ping
  • livestorm_register_person
  • livestorm_remove_tag
  • livestorm_unregister_person
  • livestorm_unregister_person_by_email
  • livestorm_update_event
  • livestorm_update_session
  • livestorm_update_session_contact

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The OAuth grant is coarser than Livestorm's own API tokens. The MCP server advertises two scopes, full:read and full:write. Livestorm's REST API offers four independent scope families — identity, events, admin and webhooks — each with read and write, and its API reference marks individual endpoints with events:read, events:write, admin:write and webhooks:write. A Livestorm API token can be issued that reads events but cannot touch team members. The MCP consent screen cannot express that distinction. Granting write access grants deleting a team member and creating a webhook alongside registering an attendee.
  • No boundary sits between the routine write and the irreversible one. full:write covers livestorm_register_person and livestorm_delete_event identically.
  • Deletions are documented as permanent. Livestorm states that removing a registrant cannot be undone, applies across every session of the event, and also deletes that person's chat messages and questions. Deleting a team member permanently deletes their polls, chat messages and answers, and reassigns their email templates to the workspace owner.
  • Registration sends mail and the connector gives no warning. Covered above; the tool description surface we could read does not mention it, and neither does Livestorm's MCP page.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here beyond what Livestorm's REST reference documents for the equivalent endpoint.
  • The Public API is off by default and gated on support. Livestorm requires you to contact support to activate it, so the connector cannot be tried on a fresh workspace unassisted.
  • Rate limits are tight for bulk work. Ten thousand calls per 30 days and five per second. Livestorm's own registration documentation warns that creating multiple registrants will hit the burst limit unless you throttle. Raising the monthly quota is an add-on purchase restricted to Business and Enterprise plans; the per-second limit cannot be raised at all.
  • Revoked team members keep working tokens. Livestorm documents that removing a team member does not delete their API tokens, which "remain active and usable" until someone revokes them manually. That is an API-token property rather than an OAuth one, but it governs the same underlying API.
  • A second, unrelated Livestorm MCP server exists. https://developers.livestorm.co/mcp is a ReadMe-hosted documentation-search server, advertised in that host's Link headers with the server name com.readme/livestorm. It searches the docs; it holds no webinar data. Do not configure it expecting the tools on this page.
  • Livestorm publishes no tool descriptions. Its MCP page describes the surface in one sentence and points at no list, so every per-tool behaviour on this page is inferred from the REST endpoint the tool name matches. The mapping is unambiguous — 41 names, 41 endpoints — but it is our mapping, not Livestorm's.

Frequently asked questions

Does registering someone through the Livestorm MCP server send them an email?

Yes, if the event has a confirmation email switched on. Livestorm's support documentation states that automatic emails set up on an event, such as the registration confirmation email, are triggered as soon as a programmatic integration adds participants. The tool takes an email address as a parameter, so a single agent call reaches a real person's inbox.

How many tools does the Livestorm MCP server have?

Forty-one, and Livestorm's own server confirms that number. Its unauthenticated health endpoint reported toolCount 41 on 2026-08-22, matching Anthropic's directory listing exactly. Livestorm's documentation never enumerates the tools in prose, describing them only as a set covering events, sessions and people, so the health endpoint is the vendor-side confirmation.

What OAuth scopes does the Livestorm MCP server request?

Two: full:read and full:write. Livestorm's RFC 9728 resource descriptor and its authorization server metadata both advertise exactly that pair. There is no scope separating reading a webinar from deleting one, so any client granted write access can delete events, sessions, team members and registrants.

Can the Livestorm connector delete a webinar or a registrant?

Yes, and Livestorm documents both as permanent. Seven of the 41 tools carry destructive verbs, covering events, sessions, team members, webhooks, tags and registrants. Livestorm's support article on removing a registrant states the action is permanent, applies to every session of an event, and cannot be undone.

What personal data can the Livestorm MCP server read?

Attendee contact details and everything they typed during a webinar. The people endpoints return email, first and last name, timezone and avatar link for anyone who registered or attended. Separate tools return session chat messages and audience questions, so text written by attendees enters the agent's context directly.

Do I need a paid Livestorm plan to use the MCP server?

You need a Livestorm account with the Public API switched on, which Livestorm does not enable by default. Livestorm's documentation states the Public API must be activated on your workspace and that you should contact support to have it turned on. Only the workspace owner and admins can generate the underlying API tokens.

What are the Livestorm API rate limits?

Ten thousand calls per rolling 30-day period, and five requests per second. Livestorm's rate limits documentation describes both, returns HTTP 429 when either is exceeded, and supplies Retry-After and RateLimit-Reset headers. The monthly quota can be raised by buying an add-on on Business and Enterprise plans; the burst limit cannot be changed.

Can the Livestorm connector send data to a server I do not control?

Yes, through webhook creation. The create-webhook tool takes an arbitrary HTTPS URL and an event name, and Livestorm then POSTs matching payloads to it. Livestorm's webhooks guide states a subscription applies to every event and session in the workspace with no per-session filtering, so one call can stream all future registration data outward.

Why does the Livestorm MCP server ask for admin rights?

Because three of its tools act on your team, not your webinars. The connector can create a team member, list all team members and delete one. Livestorm's Public API documents those endpoints as requiring an admin scope, and its support article states only the workspace owner and admins can generate API tokens at all.

Sources

More Sales & CRM connectors

  • Abency

    Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.

  • Actively

    Read per-account sales intelligence — agent memory, decisions, signals — from an AI agent.

  • Adobe Journey Optimizer

    Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Livestorm to work.

Connect Livestorm once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio