ZegoCloud MCP for AI. Control real-time chat, streams, and users from plain language.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
ZegoCloud MCP handles real-time communication control, letting your agent moderate video/voice chats and send messages programmatically. Use it to kick out disruptive users from virtual rooms, stop live streams instantly by ID, or manage private peer-to-peer messaging without touching an admin dashboard.
What AI agents can do with ZegoCloud Automation
Kickout user
This tool removes a specific user from a given virtual room.
Send peer message
It sends a private, text-based message between two specified users.
Stop publish
This command manually ends an active video or audio stream broadcast using its unique ID.
The agent can instantly eject specific users from any virtual room by calling the kickout_user tool.
You can send text messages directly between two users using the send_peer_message tool, regardless of whether they are in a public room.
The agent terminates active streaming sessions immediately by supplying the unique stream ID to stop_publish.
Ask an AI about this
Waiting for input…
What AI agents can do with ZegoCloud MCP: 3 Tools
These tools give you immediate command over user moderation, private messaging, and live streaming control for any communication environment.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ZegoCloud on VinkiusKickout User
This tool removes a specific user from a given virtual room.
Send Peer Message
It sends a private, text-based message between two specified users.
Stop Publish
This command manually ends an active video or audio stream broadcast using its...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ZegoCloud, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The sheer number of clicks needed for real-time moderation is exhausting., Solved with Vinkius AI Gateway
Right now, when a live event goes wrong—a user needs to be removed or a stream needs shutting down—you have to jump between the main dashboard, the user list, and the chat logs. It’s clicking through three different tabs just to execute one simple command.
With this MCP, you simply talk to your agent. You tell it to kick out an unauthorized user or stop a rogue stream. The result is that the action executes immediately from your single chat window. It keeps you focused on the event, not the interface.
ZegoCloud MCP gives you control over participants and streams.
The manual steps of tracking user IDs, finding the correct stream ID, and then executing a separate action for each one are gone. Your agent handles the entire sequence based on your natural language prompt.
You move from reactive clicking to proactive commanding. You manage complex communication environments with simple instructions.
What your AI can actually do with this
You can connect ZegoCloud's infrastructure to any AI client to manage and control real-time video, voice, and text environments using plain language instructions. This lets your agent handle moderation tasks—like kicking out disruptive participants or sending technical messages—as if a human operator was typing the commands into an internal dashboard.
Managing these live interactions used to mean constantly switching tabs and running around manually. Now, you simply tell your agent what needs to happen. You can manage communication rooms entirely from your chat window. Because ZegoCloud handles all connections through Vinkius, you get full visibility via Vinkius AI Analytics; nothing happens in the dark.
This audit trail lets you see exactly which moderation actions were taken and when they occurred, keeping a clean record of every interaction.
019ea611-5c1b-723f-a7e5-cfd3027d9557 Here's how it actually works
The bottom line is you stop using dashboards and start talking directly to the system.
First, subscribe to this MCP and input your ZegoCloud App ID, Server Secret, and API URL.
Next, connect your preferred AI client (like Claude or Cursor) from that single point of connection. You'll never have to manage credentials outside the platform.
Finally, prompt your agent with natural language instructions—for example, 'Stop the broadcast for stream ID XYZ'—and it executes the command.
Who is this actually for?
This MCP is built for operational roles that need real-time control over communications but don't have time to click through multiple vendor dashboards. It’s for people who manage live events, support large user bases, or develop complex communication logic.
The moderator needs to instantly remove users causing trouble or halt unauthorized broadcasts during a massive virtual event without physically being in the control room.
The engineer uses it to send technical messages directly to a client user, bypassing standard chat channels for critical troubleshooting steps.
The developer runs tests and manages complex RTC workflows—like simulating kickouts or stream stops—right from the code editor without needing dedicated admin console access.
What Changes When You Connect
Moderation becomes instant. You can tell your agent to execute the kickout_user tool if a participant breaks rules; no manual clicking is needed.
Never worry about orphaned streams again. Use the stop_publish tool to halt any broadcast instantly just by giving it the stream ID.
Support communication improves dramatically when you use send_peer_message, allowing your agent to talk directly to a client user without them having to initiate contact.
Managing rooms is easier than ever. You can orchestrate complex messaging and moderation tasks across multiple users through one simple prompt.
You keep perfect records of everything. Vinkius AI Analytics ensures that every kickout_user action or stream stop has an immutable, auditable trail attached to it.
See it in action
Handling a disruptive attendee during a conference
A moderator notices a user spamming the chat. Instead of manually logging into the admin panel, they prompt their agent: 'Kick user X from room Y for harassment.' The kickout_user tool runs immediately, resolving the issue without delay.
Diagnosing a connection failure post-launch
A support engineer knows a client is having audio issues. They use send_peer_message to send specific diagnostic commands directly to the user's chat window, bypassing public announcements and getting immediate feedback.
Ending an unauthorized stream broadcast
Someone starts broadcasting sensitive material unexpectedly. The agent is prompted with 'Stop streaming for ID 12345.' It calls stop_publish immediately, terminating the content feed before damage can be done.
Automating post-event cleanup
An event manager needs to ensure all streams end after a session. They chain commands, first calling kickout_user for departing users, and then running stop_publish on every associated stream ID in sequence.
The honest tradeoffs
Trying to manage moderation via general chat prompts
Writing a long message like: 'Can you please kick out this person and also send them a warning.' This is vague, requires multiple steps, and might fail.
Use the specific tools. For moderation, call kickout_user with all necessary parameters in one command. If you need to warn them afterward, follow up with send_peer_message.
Assuming a simple 'undo' function
Thinking that simply telling the agent 'Undo what you just did.' The system doesn't have state memory for rollbacks.
The platform is designed for declarative actions. If an action fails, manually check the audit log through Vinkius AI Analytics to see exactly where the process broke.
Relying on a single tool for all needs
Using only send_peer_message when a user is disruptive. This sends a message but doesn't solve the root problem.
You need to chain tools. First, use kickout_user to remove the person, and then use send_peer_message to notify other users that the moderation action occurred.
When It Fits, When It Doesn't
Use this MCP if your primary workflow involves real-time control over active communication sessions—you need to moderate people, stop feeds, or manage direct chat. Don't use it if you only need historical data; for logs and records, look at a dedicated database connector. If all you need is basic messaging without the ability to kick users or stop streams, a simpler messaging-only MCP might suffice. But if control, security, and immediate action are mandatory, this ZegoCloud MCP gives you that operational depth.
Questions you might have
Can I remove a specific user from a video room if they are violating terms? +
Yes. Use the kickout_user tool by providing the Room ID and User ID. You can also include a custom reason for the removal.
How do I stop a live stream that is currently broadcasting? +
Simply use the stop_publish tool with the specific Stream ID. This will immediately terminate the broadcast for that stream.
Is it possible to send a private system command to a user's application? +
Yes. The send_peer_message tool allows you to send messages with type '2' (Command), which can be used to trigger logic within the recipient's app.
How does Vinkius handle authentication when I use the `kickout_user` tool? +
Your credentials pass through a zero-trust proxy and are never stored on disk. Vinkius handles all secret management, so you don't worry about key persistence or security risks when calling this MCP.
If I run `send_peer_message` with an invalid recipient ID, what kind of error response should I expect? +
The system returns a clear status code and message detailing the failure. This allows your agent to catch the specific API exception and retry or notify the user correctly.
Are there rate limits for calling `stop_publish` on multiple streams in quick succession? +
While there are internal platform limitations, Vinkius optimizes calls with native token support. You can manage many streams efficiently without hitting typical usage caps.
When I use the `send_peer_message` tool, is the message scope restricted to the current virtual room? +
Yes, the messaging tool keeps communication contained within the defined context. This ensures that peer-to-peer messages stay relevant and scoped correctly for the users in that specific chat environment.
Does running `kickout_user` generate an auditable record of the moderation action? +
Every tool call generates a cryptographically signed audit trail. You get a tamper-proof log recording who, when, and why the user was kicked from the room.
We've already built the connector for ZegoCloud. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.