2,500+ MCP servers ready to use
Vinkius

100ms MCP Server for CrewAI 9 tools — connect in under 2 minutes

Built by Vinkius GDPR 9 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="100ms Specialist",
    goal="Help users interact with 100ms effectively",
    backstory=(
        "You are an expert at leveraging 100ms 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 100ms "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
100ms
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 100ms MCP Server

Connect your 100ms account to any AI agent and manage your live video infrastructure through natural conversation.

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

What you can do

  • Room Management — List all virtual rooms, retrieve deep technical metadata, and create new rooms with specific templates and descriptions
  • Session Monitoring — Monitor active or completed video sessions in real-time and retrieve session history across your organization
  • Participant Governance — List all peers (participants) currently in a session and retrieve their unique IDs and roles
  • Peer Control — Remotely remove or kick participants from active sessions with custom reasons directly from your agent
  • Recording Discovery — List and browse cloud recordings, filtered by room or status (completed, failed, or processing)
  • Operational Insights — Quickly find unique room, session, and peer IDs required for automated video workflows
  • Scalable Infrastructure — Verify your live video configurations and template settings through automated metadata retrieval

The 100ms MCP Server exposes 9 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 100ms to CrewAI via MCP

Follow these steps to integrate the 100ms MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from 100ms

Why Use CrewAI with the 100ms MCP Server

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

01

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

02

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

03

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

04

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

100ms + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

100ms MCP Tools for CrewAI (9)

These 9 tools become available when you connect 100ms to CrewAI via MCP:

01

create_room

Use this when the user asks to start or host a new meeting space. Create a new video room

02

get_room

Requires the unique room ID. Get the configuration and details of a specific video room

03

get_session

Get the details and metadata of a specific video session

04

list_peers

Requires the session ID. List all participants currently inside an active video session

05

list_recordings

Can optionally filter by room ID or the status of the recording. List cloud recordings of video rooms

06

list_rooms

Use this to find a room ID. List all video rooms in the 100ms account

07

list_sessions

You can filter by room ID or status. Use this to find who attended past meetings. List active or past video sessions

08

remove_peer

Requires the session ID and the peer ID. Kick or remove a specific participant from an active video session

09

update_room

Requires the room ID. Update the settings of an existing video room

Example Prompts for 100ms in CrewAI

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

01

"List all my video rooms in 100ms."

02

"Are there any active sessions for the 'Town Hall' room right now?"

03

"Remove participant 'peer-123' from the session 'sess-abc' for 'violating community guidelines'."

Troubleshooting 100ms MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

Rate limiting or 429 errors

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

100ms + CrewAI FAQ

Common questions about integrating 100ms MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect 100ms to CrewAI

Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.