Can I get a direct download link for a past meeting recording?

Yes. The `get_recording_details` tool allows your AI agent to retrieve the full metadata for any cloud recording, including a temporary direct download link for the MP4 file.

How do I change the branding colors of my meeting room?

You can use the `update_room_theme` tool. Provide the room name and your preferred hex color code, and your agent will update the primary branding color for that specific space instantly.

Can I create a room that requires my approval before others can join?

Yes. When using the `create_meeting_room` tool, you can set the `is_locked` parameter to true. This ensures the room is locked by default, and participants must 'knock' to be allowed in by the host.

Whereby MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Whereby
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Whereby through the Vinkius — pass the Edge URL in the `mcps` parameter and every Whereby tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Whereby Specialist",
    goal="Help users interact with Whereby effectively",
    backstory=(
        "You are an expert at leveraging Whereby tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Whereby "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Whereby MCP Server

Connect your Whereby account to any AI agent and manage your video communication infrastructure through natural conversation.

When paired with CrewAI, Whereby becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Whereby tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Meeting Creation — Instantly provision new transient video meeting rooms with specific expiration dates and room modes (normal or group)
Meeting Insights — Retrieve full details for any meeting, including the exact join URL and real-time status
UI Customization — Update and manage visual room themes, including custom colors and branding, to match your application's look and feel
Recording Management — List all cloud recordings stored in your account and retrieve direct MP4 download links and metadata
Active Sessions — Monitor currently active or pending meeting rooms and retrieve their unique UUIDs for automated workflows
Data Integrity — Safely delete obsolete meeting rooms or cloud recordings to manage your quotas and storage efficiently
Room Controls — Configure room security by setting rooms to 'locked' mode, requiring host approval for new participants

The Whereby MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Whereby to CrewAI via MCP

Follow these steps to integrate the Whereby MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Whereby

Why Use CrewAI with the Whereby MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Whereby through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Whereby + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Whereby MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Whereby for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Whereby, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Whereby tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Whereby against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Whereby MCP Tools for CrewAI (10)

These 10 tools become available when you connect Whereby to CrewAI via MCP:

create_meeting_room

Provide an ISO 8601 end date and room mode (normal or group). Creates a new transient video meeting room with a specific end date

delete_cloud_recording

This action is irreversible. Permanently deletes a cloud recording file

delete_meeting_room

This action is irreversible. Immediately deletes a video meeting room and terminates any active session

get_meeting_details

Retrieves details for a specific video meeting, including its join URL and expiration date

get_recording_details

Retrieves download links and metadata for a specific cloud recording

get_room_theme

Retrieves the visual theme settings (colors, logo) for a specific room name

list_active_meetings

Lists all currently active or pending video meeting rooms created via the API

list_cloud_recordings

Lists all cloud recordings stored in the Whereby account

reset_room_theme

Resets a meeting room theme back to the default Whereby branding

update_room_theme

Provide the room name and a hex color code. Updates the primary branding color for a specific meeting room

Example Prompts for Whereby in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Whereby immediately.

"Create a new 'group' meeting room that expires in 2 hours."

"List all my past cloud recordings."

"Update the 'Support-101' room theme to use hex color #00ff00."

Troubleshooting Whereby MCP Server with CrewAI

Common issues when connecting Whereby to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Whereby + CrewAI FAQ

Common questions about integrating Whereby MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.