How to Use the MeetingPulse MCP in VS Code Copilot

Q: How does my team share the MeetingPulse configuration in VS Code Copilot?

Save the MeetingPulse configuration in your project's .vscode/mcp.json file to configure the MCP Server for everyone using VS Code Copilot. Every developer in that repo will instantly have access.

Q: Can I use VS Code Copilot to search for specific MeetingPulse sessions?

Yes, the searchmeetings tool allows your VS Code Copilot agent to find MeetingPulse sessions by name or keyword. You can quickly retrieve the exact meeting ID you need for debugging.

Share real-time MeetingPulse analytics and audience metrics across your entire team inside VS Code Copilot.

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 VS Code Copilot

Create your Vinkius account to connect MeetingPulse to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Commit team-wide MeetingPulse tools in VS Code Copilot

The `list_meetings` tool gives your entire engineering team instant access to active MeetingPulse session data inside VS Code Copilot. By adding this MCP Server to your `.vscode/mcp.json` file, everyone on the repo gets the same tools. Your team uses VS Code Copilot to write, test, and debug integrations using real MeetingPulse account data. This shared configuration keeps everyone aligned without manual setup.

Inspect live MeetingPulse poll details in VS Code Copilot

The `get_poll_details` tool pulls specific MeetingPulse poll structures directly into your VS Code Copilot chat window. This MCP tool lets you verify how your frontend component renders different question types. Your VS Code Copilot agent references active polls via `list_polls` to suggest UI styling improvements for your MeetingPulse frontend. It makes building audience-facing interfaces much more reliable.

Audit shared MeetingPulse files and attendee lists with Copilot

The `list_meeting_files` tool retrieves all files uploaded to a MeetingPulse session directly inside VS Code Copilot. Your agent can verify file names and formats without leaving the IDE. Your VS Code Copilot agent combines this with `list_attendees` to check who has access to specific MeetingPulse materials. This helps you build secure, compliant event portals.

Setup guide

Set up MeetingPulse MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the MeetingPulse MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the MeetingPulse tools listed. Try asking: "List my recent MeetingPulse transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Save the MeetingPulse configuration in your project's `.vscode/mcp.json` file to configure the MCP Server for everyone using VS Code Copilot. Every developer in that repo will instantly have access.

Yes, the `search_meetings` tool allows your VS Code Copilot agent to find MeetingPulse sessions by name or keyword. You can quickly retrieve the exact meeting ID you need for debugging.

It runs through the Vinkius zero-trust environment which is fully compatible with enterprise security policies, ensuring your team can use the MeetingPulse MCP Server safely inside VS Code Copilot.

Open Copilot Chat inside VS Code, switch to Agent mode, and ask it to list your active MeetingPulse meetings. The agent will use the server to retrieve the list.

All MeetingPulse session metadata and Q&A strings remain secure within your local VS Code Copilot session via the Vinkius gateway.

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