4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Liveblocks MCP Server

Bring Real Time Collaboration
to CrewAI

Learn how to connect Liveblocks to CrewAI and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Authorize UserBroadcast EventCreate RoomCreate ThreadDelete RoomGet RoomGet StorageGet ThreadGet YdocIdentify UserInitialize StorageList Active UsersList RoomsList ThreadsPatch StorageResolve ThreadUpdate RoomUpdate Ydoc

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Liveblocks

What is the Liveblocks MCP Server?

Connect your Liveblocks account to any AI agent to orchestrate multiplayer experiences and real-time collaboration features through natural language.

What you can do

  • Room Management — List, create, update, and delete rooms to manage your application's collaborative spaces.
  • User Authentication — Generate access tokens and identify users with specific permissions using authorize_user and identify_user.
  • Collaborative Storage — Inspect and patch room storage state or manage Yjs documents for shared editing.
  • Comments & Threads — Query, create, and resolve comment threads to keep track of team discussions within rooms.
  • Real-time Presence — List active users in a room or broadcast custom events to connected clients.

How it works

  1. Subscribe to this server
  2. Enter your Liveblocks Secret Key
  3. Start managing your real-time infrastructure from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Full-stack Developers — quickly debug room storage, manage user permissions, or clear stale rooms without leaving the terminal or IDE.
  • Product Managers — monitor active collaboration sessions and review comment threads across different project rooms.
  • DevOps Engineers — automate the provisioning of collaborative environments and manage access rules programmatically.

Built-in capabilities (18)

authorize_user

Obtain an access token for a client to enter a room

broadcast_event

Broadcast a JSON event to a room

create_room

Create a new room

create_thread

Create a thread and the first comment

delete_room

Delete a room

get_room

Retrieve room details

get_storage

Get the room's Storage tree

get_thread

Get a specific thread

get_ydoc

Get a JSON representation of the Yjs document

identify_user

Permissions are managed on the backend. Obtain an ID token for a client

initialize_storage

Initialize or reinitialize Storage

list_active_users

List users currently in the room

list_rooms

Can be filtered by metadata or access. List rooms with filtering and pagination

list_threads

List threads in a room

patch_storage

Apply JSON Patch operations to Storage

resolve_thread

Resolve a thread

update_room

Update room properties

update_ydoc

Send a binary Yjs update

Why CrewAI?

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

  • 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 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

See it in action

Liveblocks in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Liveblocks and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Liveblocks to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Liveblocks in CrewAI

The Liveblocks 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. All 18 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Liveblocks
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

The Vinkius Advantage

How Vinkius secures Liveblocks for CrewAI

Every tool call from CrewAI to the Liveblocks MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I filter rooms by specific metadata using the AI?

You can ask the agent to use the list_rooms tool and provide a JSON string in the metadata parameter. For example, ask to 'List rooms where the project metadata is alpha'.

02

Can I generate a temporary access token for a user to join a room?

Yes. Use the authorize_user tool. Provide the Room ID and User ID, and the agent will return a token that grants access to that specific room.

03

Is it possible to permanently delete a room and its data?

Yes, the delete_room tool allows you to permanently remove a room and all associated storage, comments, and metadata. Use this with caution as it is irreversible.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →