How to Use the Demio MCP in CrewAI

Q: How does CrewAI handle Demio registrations?

You assign a specific intake agent the registeruserforwebinar tool. When a user asks to sign up, that agent validates their input and executes the registration autonomously.

Deploy specialized agent teams to run your webinars. Give CrewAI access to Demio for autonomous event operations.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Demio MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign a CrewAI Demio researcher

Stop manually digging through past events to find performance trends. Spin up a specialized researcher agent and hand it the `list_webinar_events` and `get_webinar_details` tools. This agent can crawl your entire history, mapping out topics and dates. It stores this context in shared memory, allowing the rest of the crew to reference the data without making duplicate API calls.

Monitor attendance with this MCP Server

You can build a hierarchical crew where a monitor agent watches active sessions. It periodically runs `get_session_details` to track how many people actually showed up versus registered. If the drop-off rate hits a certain threshold, the monitor escalates to a moderator agent. The moderator can then trigger engagement tactics or alert the human host to change their presentation pacing.

Automate post-event reporting

Running reports takes hours of manual formatting. Create a sequential execution pipeline where the first agent calls `get_webinar_report` to grab the raw analytics. An analyst agent then takes those numbers, compares them against your `get_account_metadata` limits, and writes a performance brief. The whole process runs autonomously the minute a session ends.

Setup guide

Set up Demio 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 Demio tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Demio 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="Demio Analyst",
        goal="Access and analyze Demio data via MCP.",
        backstory="Expert analyst with direct Demio access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Demio 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 Demio. 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 Demio 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 Demio MCP in CrewAI

Just pass your Vinkius endpoint URL directly into the mcps array when defining your Agent. The framework automatically parses the available MCP tools and gives the agent access.

You definitely want to restrict access based on roles. Use MCPServerHTTP from crewai.mcp and apply a tool_filter so your reporting agent only sees read-only tools like get_webinar_report.

You assign a specific intake agent the register_user_for_webinar tool. When a user asks to sign up, that agent validates their input and executes the registration autonomously.

No custom code is required. The MCP standard handles the translation between your Python crew and the underlying REST API.

Data never rests on our servers. When your crew pulls user lists via list_webinar_registrants, the operation runs inside a temporary V8 Isolate that gets destroyed the millisecond the request finishes.

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