How to Use the MeetingPulse MCP in CrewAI

Q: Can multiple CrewAI agents use MeetingPulse tools simultaneously?

Yes, agents share the toolset and can invoke tools like getpolldetails or listmeetings as needed. The framework handles the execution sequence based on your crew's hierarchical or sequential design.

Deploy specialized agent teams to analyze and moderate your MeetingPulse sessions using CrewAI.

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 CrewAI

Create your Vinkius account to connect MeetingPulse to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Analyze Events with a CrewAI MCP Server

This MCP Server lets your CrewAI agents use `get_meeting_analytics` and `list_polls` to run post-event reviews. You assign one agent to pull the raw poll results, while a second agent compares those numbers against past performance. They collaborate in the background to write a detailed summary of the event. CrewAI's shared memory means the analyzing agent remembers context from prior meetings found via `list_meetings`. Your agents spot long-term engagement trends without you manually passing variables between them.

Moderate Live Q&A Sessions with Agent Teams

The `list_qa_sessions` tool gives your agent crew instant access to the audience's active question queue. One agent pulls the raw questions, a second filters out the spam, and a third drafts potential answers for your speaker. This entire pipeline runs autonomously, keeping your live Q&A clean. When a tough technical question pops up, the crew uses `search_meetings` to check how you answered similar queries in past sessions. It gives your agents an instant historical reference to maintain consistent answers.

Map Attendee Engagement and Shared Files

Using `list_attendees` and `list_meeting_files` lets your crew build detailed profiles of participant activity. One agent maps out who showed up, while another tracks which shared resources got downloaded. This division of labor gets you much deeper insights than a basic CSV export. Your crew manages the execution sequence, passing the attendee list straight to the analysis agent. You get a fully polished report delivered right to your team's Slack channel.

Setup guide

Set up MeetingPulse MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke MeetingPulse tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="MeetingPulse Analyst",
    goal="Access and analyze MeetingPulse data via MCP.",
    backstory="Expert analyst with direct MeetingPulse access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent MeetingPulse transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="MeetingPulse Analyst",
        goal="Access and analyze MeetingPulse data via MCP.",
        backstory="Expert analyst with direct MeetingPulse access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent MeetingPulse transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You configure your endpoint token on Vinkius and pass the secure server URL directly into your agent's `mcps` list. CrewAI handles the connection setup, letting your agents use the tools immediately.

Yes, agents share the toolset and can invoke tools like `get_poll_details` or `list_meetings` as needed. The framework handles the execution sequence based on your crew's hierarchical or sequential design.

You can assign a specialized agent to filter the results of `list_attendees` before passing them to other agents. This keeps the context window clean and prevents your LLM costs from spiking.

This setup supports standard stdio, SSE, and HTTP transports. You can run your crew locally or deploy it to a cloud environment without changing your tool configuration.

All Q&A session logs and poll metrics are retrieved through zero-trust ephemeral sandboxes. Vinkius secures the API tokens, ensuring your private corporate discussions and audience feedback are never exposed to external logs.

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