MeetingPulse MCP for AI. Analyze who said what, and how engaged they were.

Q: How do I find out which meetings happened last month using MeetingPulse MCP Server?

Run listmeetings. You can usually filter or search the output by date range, giving you a comprehensive list of all sessions that occurred in your desired period.

Q: Can I get poll results for multiple meetings at once with MeetingPulse MCP Server?

You need to list the polls first. Run listpolls on several meeting IDs, then loop through those IDs and call getpolldetails for each one individually to compile a full comparison.

Q: Does MeetingPulse MCP Server track who attended meetings?

Yes. Use the listattendees tool and provide the specific meeting ID. It returns a list of every participant that was logged for that session.

Q: How do I search for an old meeting using MeetingPulse MCP Server?

Use searchmeetings. This function allows you to pass keywords or phrases, and it searches across the meeting titles or descriptions rather than requiring you to know the exact ID.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

MeetingPulse connects your AI client directly to your meeting data. It lets you pull structured records for everything from poll results and Q&A logs to detailed attendance lists and overall engagement metrics.

Your agent can read all that live audience feedback and turn it into usable reports without you leaving the chat window.

What your AI can do

Get account info

Retrieves general account information for the MeetingPulse service.

Get meeting

Gets full configuration details for a single, specified meeting.

Get meeting analytics

Pulls aggregated engagement metrics and performance data for one meeting ID.

+ 7 more capabilities included

List and search meetings

Retrieve a list of all meetings, or find specific sessions using keywords.

Get meeting details and analytics

Fetch full configuration data for a single meeting, including overall engagement metrics.

Analyze poll results

Pull detailed outcomes from specific polls associated with any given meeting.

Manage attendees and files

List every person who attended a meeting, or retrieve materials shared during the session.

Track Q&A sessions

List all questions asked and answered during a specific meeting's interactive phase.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

MeetingPulse MCP Server: 10 Tools for Meeting Analysis

Use these tools with your AI agent to gather meeting details, pull live poll results, and generate deep analytics across all recorded sessions.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using MeetingPulse on Vinkius

Get Account Info

Retrieves general account information for the MeetingPulse service.

Get Meeting

Gets full configuration details for a single, specified meeting.

Get Meeting Analytics

Pulls aggregated engagement metrics and performance data for one meeting ID.

Get Poll Details

Retrieves the specific results, options, and summary data for a single poll.

List Attendees

Lists all individual users who participated in a given meeting.

List Meeting Files

Fetches a list of materials or documents that were shared during the session.

List Meetings

Generates a comprehensive list of all meetings, both active and past.

List Polls

Retrieves a summary list of polls that took place within a meeting.

List Qa Sessions

Lists all the Q&A sessions, allowing you to select one for deeper review.

Search Meetings

Finds meetings by executing a search query across titles or descriptions.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The MeetingPulse integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "meetingpulse": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the MeetingPulse tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"meetingpulse": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with MeetingPulse, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MeetingPulse. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Sifting through meeting notes and reports takes forever.

Today, pulling a complete picture of a session means jumping between three different places: the attendance roster, the poll results spreadsheet, and the dedicated Q&A tab. You copy names from one page, download files from another, and then try to manually match which question belongs to which polling outcome.

With MeetingPulse MCP, you tell your agent what you need—'Give me everything about meeting ABC.' The agent runs the necessary tools (`list_attendees`, `get_poll_details`, `list_qa_sessions`) and returns a single block of structured data. You get the whole story without lifting a finger.

MeetingPulse MCP Server: Track real-time engagement metrics.

Before, finding out if polls were correlated with attendance required exporting three separate files and cross-referencing the dates. It was tedious, error-prone manual data wrangling every time you needed to prove ROI.

Now, your agent handles it. You prompt for 'Engagement report for last week.' The server runs `get_meeting_analytics` and pulls in all the required metrics—the numbers, not just the graphs. It's immediate.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

You hook up your AI client to MeetingPulse and you get full read access to all your meeting data through natural conversation. This server lets your agent pull structured records for everything—from poll results and Q&A logs to attendance lists and overall engagement metrics. Your agent reads all that live audience feedback and turns it into usable reports without you ever leaving the chat window.

Listing and Searching Meetings: You can get a full rundown of every meeting, both active and past, by invoking list_meetings. If you know what you're looking for, you don't have to scroll through everything; instead, run search_meetings with keywords to find specific sessions based on titles or descriptions. For any single session you zero in on, you can pull the full setup details using get_meeting, which provides all the configuration data for that one meeting.

Analyzing Meeting Performance: To see how well a meeting went overall, run get_meeting_analytics against a specific meeting ID; this pulls aggregated performance metrics and general engagement numbers. You can also get a quick summary of every poll that ran during a session by calling list_polls. If you need the deep dive on one particular survey, use get_poll_details to retrieve the precise results, available options, and full summary data for that single poll.

Managing Participants and Materials: You can list every individual who showed up at a meeting using list_attendees, providing names and participation records. When you need to know what materials were shared, run list_meeting_files to fetch all the documents or assets distributed during the session. For tracking interactive phases, use list_qa_sessions to get a list of all Q&A sessions that happened; once you've selected one, your agent can then review it for deeper insight into questions and answers.

Core Functionality: Beyond these specific data pulls, you can always check the basic operational health of the connection by running get_account_info, which retrieves general account setup information for MeetingPulse. You’ll never have to switch tabs or jump between different dashboard tools; your agent handles all this complexity right in the chat.

If you're looking at a specific meeting, remember that calling list_meetings gives you the roster of every session. If you need granular details on one event, use get_meeting. When performance numbers are key, you run get_meeting_analytics. For figuring out who showed up and what they talked about, your agent uses list_attendees and list_qa_sessions, respectively.

You can pull the list of shared documents with list_meeting_files, or find specific poll outcomes by getting a summary list with list_polls and then detailing the results using get_poll_details. If you need to narrow down your search, just hit up search_meetings.

Built · Hosted · Managed by Vinkius MeetingPulse MCP Server - Track Meeting Analytics & Polls

Server ID 019d75d1-8321-72fa-99c8-155324edf1ce

Vinkius Inspector

Compliance Grade A+

Score 98.33/100

Report View Report ↗

Here's how it actually works

The bottom line is: you use natural language with your AI client; the server handles all the API calls and spits out organized data.

Subscribe to the MeetingPulse server on Vinkius and provide your API key.

Your AI client executes a tool call (e.g., list_meetings) specifying required parameters like date ranges or keywords.

The server runs the function, fetches the live data from MeetingPulse's backend, and returns clean, structured JSON to your agent.

Who is this actually for?

This is for anyone who has to compile reports about group discussions. Think event managers, product marketers, or BI analysts who spend too much time clicking through dashboards at 2 am trying to stitch together poll results with attendance lists. If your job involves proving 'what happened' after a meeting, you need this.

Event Manager

They use list_meetings and then run get_meeting_analytics to quickly prove the success metrics of an event day without manually pulling reports.

Product Marketing Manager

Needs to know what users cared about. They'll call get_poll_details and then list_qa_sessions to build a narrative on product pain points post-launch.

Business Intelligence Analyst

Uses the full suite—from list_attendees to running multiple queries against get_meeting_analytics—to correlate participant behavior with overall engagement rates for quarterly reports.

What Changes When You Connect

See the full picture of attendee behavior. Instead of just seeing a participant count, use list_attendees to get every name and profile associated with the meeting ID.

Pinpoint exactly where interest dropped off. By running get_meeting_analytics, you don't just see 'low engagement'; you get metrics on which segment or time window was weakest.

Compare feedback across sessions instantly. Use list_polls to list all polls for a meeting, then use get_poll_details to pull the winning result from any of them, all in one chat thread.

Contextualize discussions with resources. You can run list_meeting_files alongside list_qa_sessions. This links the specific questions asked directly back to the materials that were shared during the session.

Stop hunting for meetings. If you remember a key word or date, use search_meetings instead of running through every single result from list_meetings. It finds it faster.

See it in action

01 01

Auditing post-event feedback

The event organizer needs to write a report showing that the new product feature was popular. They ask their agent: 'For meeting ID 456, list all polls and get details for any poll mentioning 'Feature X'. Then, pull the top three questions from Q&A.' The agent runs list_polls and get_poll_details, delivering a structured report instantly.

02 02

Investigating low attendance

The sales team needs to know why key clients didn't show up for the last webinar. They ask their agent to run search_meetings for 'Webinar 2024'. Then, they use list_attendees on the resulting meeting ID to get a list of expected participants who were actually absent.

03 03

Comparing historical performance

A BI analyst needs to prove that Q3 meetings were more engaging than Q2. They run list_meetings for both quarters, then loop through the IDs and call get_meeting_analytics on each one. The agent compiles a comparative metric table.

04 04

Quickly compiling meeting materials

A team lead needs to send out all relevant documents from a massive annual kick-off meeting. They ask the agent, 'List files for the last Annual Kick-Off.' The agent immediately calls list_meeting_files and provides the links in one block.

The honest tradeoffs

Trying to guess meeting IDs

Anti-pattern

The user tries to call get_poll_details(id=123) without first knowing that poll 123 belongs to the correct meeting. The API fails because the ID is ambiguous or non-existent.

The Fix

First, run list_meetings to find the correct Meeting ID (e.g., 'Meeting ABC'). Then, use that ID when calling other tools: get_poll_details(meeting_id='Meeting ABC'). Always anchor your calls.

Confusing polls with general questions

Anti-pattern

The user asks the agent to list all discussion points and expects poll results. The agent only sees a generic 'Q&A' tool, so it misses structured voting data.

The Fix

Use list_polls first. This ensures you see if formal polls ran in the meeting. After getting the IDs, use get_poll_details to pull the specific vote counts.

Assuming all data is available

Anti-pattern

The user expects a simple list of every attendee's job title and department from list_attendees, but the API only provides name and email.

The Fix

Be specific in your prompt. If you need role details, first check the meeting configuration using get_meeting to see what metadata is actually available for that account.

When It Fits, When It Doesn't

Use this server if your goal is data aggregation and analysis—if you need the AI client to perform multiple lookups (e.g., list meetings -> get analytics -> list attendees) and synthesize the findings into a single report, this is perfect. You're using it as an API layer over MeetingPulse.

Don't use it if all you need is simple viewing or confirmation. If you just want to check how many people attended, running list_meetings and then getting the count from the resulting list might be simpler than invoking multiple tools. Also, if your native dashboard already shows exactly what you need (e.g., a simple chart), don't add complexity. This server shines when the data is siloed or needs to be combined with other external sources.

Questions you might have

How do I find out which meetings happened last month using MeetingPulse MCP Server? +

Run list_meetings. You can usually filter or search the output by date range, giving you a comprehensive list of all sessions that occurred in your desired period.

Can I get poll results for multiple meetings at once with MeetingPulse MCP Server? +

You need to list the polls first. Run list_polls on several meeting IDs, then loop through those IDs and call get_poll_details for each one individually to compile a full comparison.

Does MeetingPulse MCP Server track who attended meetings? +

Yes. Use the list_attendees tool and provide the specific meeting ID. It returns a list of every participant that was logged for that session.

How do I search for an old meeting using MeetingPulse MCP Server? +

Use search_meetings. This function allows you to pass keywords or phrases, and it searches across the meeting titles or descriptions rather than requiring you to know the exact ID.

What do I need to use the `get_account_info` tool in MeetingPulse MCP Server? +

You must provide a valid MeetingPulse API Key. Once authenticated, your agent can pull basic account details like plan status and overall usage metrics.

Can I get granular data using the `get_poll_details` tool? +

Yes, this tool retrieves deep poll data, including individual question text, response counts, and percentages for every choice. You need to supply both the poll ID and the meeting ID.

What metrics does `get_meeting_analytics` provide? +

It gives you a summary of engagement performance. Specifically, it returns the overall participation rate, total questions asked in Q&A, and time-based activity markers for the session.

How do I check materials using `list_meeting_files`? +

The tool lists all files shared during a specific meeting. You get the file name, its unique ID, and a direct link to download the material for review.

How do I find my MeetingPulse API Key? +

Log in to MeetingPulse, go to your Profile or Integration Settings, and generate or copy your API Key from the API section.

Can I retrieve poll results in real-time? +

Yes! Use the get_poll_details tool with the meeting and poll IDs to see the current voting results.

Is my meeting data secure? +

Absolutely. Your credentials are encrypted at rest and injected securely at runtime.

Connect to your AI in seconds.

Get account info

Get meeting

Get meeting analytics

MeetingPulse MCP Server: 10 Tools for Meeting Analysis

Make your AI actually useful.

Get Account Info

Get Meeting

Get Meeting Analytics

Get Poll Details

List Attendees

List Meeting Files

List Meetings

List Polls

List Qa Sessions

Search Meetings

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Sifting through meeting notes and reports takes forever.

MeetingPulse MCP Server: Track real-time engagement metrics.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Auditing post-event feedback

Investigating low attendance

Comparing historical performance

Quickly compiling meeting materials

The honest tradeoffs

Trying to guess meeting IDs

Confusing polls with general questions

Assuming all data is available

When It Fits, When It Doesn't

Questions you might have