4,000+ servers built on vurb.ts
Vinkius

Liveblocks MCP Server for AutoGenGive AutoGen instant access to 18 tools to Authorize User, Broadcast Event, Create Room, and more

MCP Inspector GDPR Free for Subscribers

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Liveblocks as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Ask AI about this MCP Server for AutoGen

The Liveblocks MCP Server for AutoGen is a standout in the Productivity category — giving your AI agent 18 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="liveblocks_agent",
            tools=tools,
            system_message=(
                "You help users with Liveblocks. "
                "18 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
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

About Liveblocks MCP Server

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

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Liveblocks tools. Connect 18 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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.

The Liveblocks MCP Server exposes 18 tools through the Vinkius. Connect it to AutoGen in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 18 Liveblocks tools available for AutoGen

When AutoGen connects to Liveblocks through Vinkius, your AI agent gets direct access to every tool listed below — spanning real-time-collaboration, room-management, user-presence, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

authorize

Authorize user on Liveblocks

Obtain an access token for a client to enter a room

broadcast

Broadcast event on Liveblocks

Broadcast a JSON event to a room

create

Create room on Liveblocks

Create a new room

create

Create thread on Liveblocks

Create a thread and the first comment

delete

Delete room on Liveblocks

Delete a room

get

Get room on Liveblocks

Retrieve room details

get

Get storage on Liveblocks

Get the room's Storage tree

get

Get thread on Liveblocks

Get a specific thread

get

Get ydoc on Liveblocks

Get a JSON representation of the Yjs document

identify

Identify user on Liveblocks

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

initialize

Initialize storage on Liveblocks

Initialize or reinitialize Storage

list

List active users on Liveblocks

List users currently in the room

list

List rooms on Liveblocks

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

list

List threads on Liveblocks

List threads in a room

patch

Patch storage on Liveblocks

Apply JSON Patch operations to Storage

resolve

Resolve thread on Liveblocks

Resolve a thread

update

Update room on Liveblocks

Update room properties

update

Update ydoc on Liveblocks

Send a binary Yjs update

Connect Liveblocks to AutoGen via MCP

Follow these steps to wire Liveblocks into AutoGen. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token
03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration
04

Explore tools

The workbench discovers 18 tools from Liveblocks automatically

Why Use AutoGen with the Liveblocks MCP Server

AutoGen provides unique advantages when paired with Liveblocks through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Liveblocks tools to solve complex tasks

02

Role-based architecture lets you assign Liveblocks tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Liveblocks tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Liveblocks tool responses in an isolated environment

Liveblocks + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Liveblocks MCP Server delivers measurable value.

01

Collaborative analysis: one agent queries Liveblocks while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Liveblocks, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Liveblocks data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Liveblocks responses in a sandboxed execution environment

Example Prompts for Liveblocks in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Liveblocks immediately.

01

"List the first 10 rooms in my Liveblocks project."

02

"Create a new room with ID 'sprint-planning' and set default access to room:write."

03

"Who is currently active in the room 'main-editor'?"

Troubleshooting Liveblocks MCP Server with AutoGen

Common issues when connecting Liveblocks to AutoGen through Vinkius, and how to resolve them.

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Liveblocks + AutoGen FAQ

Common questions about integrating Liveblocks MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Liveblocks tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Explore More MCP Servers

View all →