How to Use the MeetingPulse MCP in Cursor

Q: How do I configure the MeetingPulse server in Cursor?

Add the MeetingPulse server details to your .cursor/mcp.json file in your project root to register this MCP Server in Cursor. Cursor will automatically load the tools for your agent.

Q: Why should I use the MeetingPulse integration inside Cursor instead of a browser?

Cursor lets your coding agent run searchmeetings to fetch real MeetingPulse data and write functional code around it. You get a faster development cycle because the AI works with live context.

Q: Does the MeetingPulse server support multi-meeting lookups in Cursor?

Yes, you can use listmeetings to fetch all active sessions from MeetingPulse inside your Cursor workspace. Your agent can then iterate through them to build custom reports.

Build custom dashboards and apps with live MeetingPulse data injected directly into your Cursor editor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MeetingPulse MCP to Cursor

Create your Vinkius account to connect MeetingPulse to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup MeetingPulse with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate code with live MeetingPulse API responses in Cursor

The `get_meeting` tool pulls actual MeetingPulse session metadata directly into your Cursor editor. This MCP integration lets you write code that interacts with real meeting structures instead of guessing the payload format. Your Cursor agent writes the integration code, tests it against live MeetingPulse endpoints, and fixes errors on the fly. This method eliminates the need for mock data during development.

Query MeetingPulse engagement metrics inside Cursor

The `get_meeting_analytics` tool delivers real-time MeetingPulse numbers straight to your active Cursor workspace. You can build analytics widgets while viewing the exact data structures they will display. Cursor reads the MeetingPulse API payload format to generate precise TypeScript interfaces. It saves you from constant documentation lookups.

Debug live MeetingPulse Q&A integrations with this MCP Server

The `list_qa_sessions` tool exposes live MeetingPulse audience questions directly inside the Cursor terminal. You see exactly how your application handles incoming questions during testing. Your Cursor agent uses `list_attendees` to map questions to specific users in your MeetingPulse code. This gives you a functional feedback loop without leaving your editor.

Setup guide

Set up MeetingPulse MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the MeetingPulse MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent MeetingPulse transactions." If the MCP tools are loaded correctly, Cursor will call the MeetingPulse tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

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

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect MeetingPulse now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about MeetingPulse MCP in Cursor

Add the MeetingPulse server details to your `.cursor/mcp.json` file in your project root to register this MCP Server in Cursor. Cursor will automatically load the tools for your agent.

The tools are read-only, meaning Cursor can retrieve details via `get_poll_details` but cannot write or edit them in MeetingPulse. This prevents accidental changes to your live events.

Cursor lets your coding agent run `search_meetings` to fetch real MeetingPulse data and write functional code around it. You get a faster development cycle because the AI works with live context.

Yes, you can use `list_meetings` to fetch all active sessions from MeetingPulse inside your Cursor workspace. Your agent can then iterate through them to build custom reports.

Vinkius runs this MeetingPulse connection inside a zero-trust, ephemeral sandbox, ensuring your raw poll metrics are never cached or stored by Cursor.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript