MeetingPulse integration
MeetingPulse is an audience engagement platform for meetings and events (live polls, brainstorming topics, pulse reactions, announcements). List, create, read, edit and delete meetings, create and remove polls one by one or in bulk and read their votes, manage brainstorming topics with their contributions and comments, edit, send or delete draft announcements, read participants, invites, email leads and audience limits, read pulse events and statistics, and manage the members of an organization. Not exposed: the login and anonymous-session routes, attendee-side actions (joining as a participant, casting a vote), routes taking a CSV or plain-text body (invite upload, posting an announcement), the pulse settings update (no documented body) and routes the vendor marks deprecated. Authentication is a permanent API token generated on the Account page of the MeetingPulse app, sent as a Bearer token in the Authorization header.
Say what should happen.
The workflow builds itself.
What you can do with MeetingPulse
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Meeting, 7 operations
create_meetingCreate meetingPOSTCreate a new meeting either from scratch or based on an existing item.delete_meetingDelete meetingDELETEIrrevocably delete the meeting and all data contained therein. Requires an *owner* role for the meeting in question.get_meetingGet meetingGETGet the full information of a meeting you own or that is shared with you. Requires any meeting role.get_meeting_statusGet meeting statusGETGet terse info on a meeting: owner, current state, participants count, your role and lifecycle timestamps.list_meetingsList meetingsGETLists data on meetings owned by the user.list_shared_meetingsList shared meetingsGETGet a list of meetings the current user has been granted roles for.update_meetingUpdate meetingPUTAlter various aspects of a meeting, including meeting status, modules, access control etc. Requires an **owner** or **presenter** role.
Poll, 7 operations
create_pollCreate pollPOSTCreate a poll in a meeting (multiple choice, rating, NPS, open text, quiz and other types).create_polls_bulkCreate polls bulkPOSTCreates several polls in a single request.delete_pollDelete pollDELETETerminates a poll and removes all data associated with it. **Meeting role** required: *owner*, *presenter* or *polls-manager*.delete_polls_bulkDelete polls bulkDELETERemoves several polls and all of their associated data in a single request.get_pollGet pollGETGet one poll of a meeting with its aggregate voting data. Meeting role required: owner, presenter, polls-manager or polls-moderator.list_pollsList pollsGETList the polls of a meeting with their properties and aggregated results, optionally only one category. Users with a meeting control role (owner, presenter, polls-manager or auditor) also receive per-user vote data.update_polls_bulkUpdate polls bulkPUTApplies metadata updates to several polls in a single request. Each item must carry its own poll "id". Updates are applied in the order provided and abort on the first failure.
Org member, 4 operations
invite_org_memberInvite org memberPOSTAdd a new organization member with the given role to the organization. Adding users is achieved through sending email invites.list_org_membersList org membersGETLists all members of a given organization. You need to be part of the organization in question.remove_org_memberRemove org memberDELETEOrganization admins can remove any member from their org, safe from themselves. Members with the "manager" role can only act on "member"-level entries.update_org_memberUpdate org memberPUTUpdate some of the membership details for an existing member or an invite for one. Only an organization admin can do that.
Topic, 4 operations
create_topicCreate topicPOSTCreate a brainstorming topic in a meeting (title, description, voting mode, moderation and display options). Meeting role required: owner, presenter or ideas-manager.delete_topicDelete topicDELETEDelete a topic and all its submitted contribution. **Meeting role** required: *owner*, *presenter* or *ideas-manager*.list_topicsList topicsGETList the brainstorming topics of a meeting with their contributions and comments. Meeting role required: owner, presenter, ideas-manager or ideas-moderator.update_topicUpdate topicPUTEdit a brainstorming topic of a meeting. Meeting role required: owner, presenter or ideas-manager.
Announcement, 3 operations
clear_announcementsClear announcementsDELETEEnsure no announcements are present in-meeting. Note that previous announcement is automatically cleared when setting a new one.delete_announcementDelete announcementDELETEDelete a single announcement from the list. Requires a **meeting role** of *owner* or *presenter*.update_draft_announcementUpdate draft announcementPUTUpdate an existing draft announcement message. This could be used to send the draft announcement using the `sent` flag. Requires a **meeting role** of *owner* or *presenter*.
Comment, 3 operations
add_commentAdd commentPOSTAdd a comment to a contribution of a brainstorming topic, optionally marked as the official response.delete_commentDelete commentDELETEDelete a comment. **Meeting role** required: *owner*, *presenter* or *ideas-manager*.update_commentUpdate commentPUTEdit a comment on a contribution of a brainstorming topic.
Contribution, 3 operations
add_contributionAdd contributionPOSTAdd a contribution (an idea or question) to a brainstorming topic.delete_contributionDelete contributionDELETEDelete a contribution and all of its submitted comments. **Meeting role** required: *owner*, *presenter* or *ideas-manager*.update_contributionUpdate contributionPUTEdit a contribution of a brainstorming topic (text, state, highlight flags).
Vote, 2 operations
list_poll_votesList poll votesGETList each participant of a meeting with all the votes they cast on the meeting polls, optionally only one poll category.list_votes_for_pollList votes for pollGETList the participants who voted on one poll of a meeting with the vote each cast (the one-poll variant of list_poll_votes).
Audience limit, 1 operation
get_audience_limitsGet audience limitsGETReturns info on who is the billable owner of a meeting, alongside the current audience limits. Any **meeting role** is required to access the data for a given meeting.
Invite, 1 operation
list_invitesList invitesGETList the would-be participants provisioned through the invitation system of a meeting.
Lead, 1 operation
list_leadsList leadsGETList the attendees who left their email (a lead) on the About/Info slide during the meeting or on the end screen of a closed meeting. Meeting role required: owner.
Participant, 1 operation
list_participantsList participantsGETReturns a hash-table of meeting participants, keyed by their internal identifier. The values in the table are participant names.
Participant vote, 1 operation
get_participant_votesGet participant votesGETGet the votes one participant cast on the polls of a meeting (the single-participant variant of list_poll_votes).
Pulse event, 1 operation
list_pulse_eventsList pulse eventsGETReturns a list of all pulse events emitted in a meeting, enumerating the users who emitted these events as well as pulse types.
Pulse setting, 1 operation
get_pulse_settingsGet pulse settingsGETReturns the current Pulse settings for all slots, along with how many slots are currently in use.
Pulse stat, 1 operation
get_pulse_statsGet pulse statsGETThis endpoint processes raw pulse events and serves aggregate data useful for drawing charts.
Video setting, 1 operation
update_video_settingsUpdate video settingsPUTAdjust some of configuration of the Video module in a meeting. Requires a **meeting role** of *owner* or *presenter*.
Use MeetingPulse from Claude Code, Cursor or Codex
Connect MeetingPulse in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its MeetingPulse operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect MeetingPulse
- Create your workspace
Sign up free. Nothing to install.
- Connect MeetingPulse once
Add your MeetingPulse connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
MeetingPulse integration FAQ
What can you do with the MeetingPulse integration?
LiveContext exposes 42 operations on MeetingPulse, covering meeting, poll, org member and topic.
