Dyte MCP. Programmatically control every aspect of your live meetings.

Listen up. This server lets your agent take full control of video calls—you can run complex live meeting workflows right from a simple chat command. It's like giving your AI client root access to your whole conferencing system, and it works.

You don't gotta write boilerplate code or mess with external API clients anymore; you just talk to the server. Your agent handles everything from setting up a new meeting room to figuring out who's recording and even pulling user lists.

Setting Up & Tracking Calls

Need a call started? You use create_meeting to spin up a brand-new Dyte video session. If you gotta check on one that's already running, you can grab the details for it with get_meeting. Want to know what meetings are floating around your account? Just run list_meetings and get a full roster.

For real-time awareness, you can set up webhooks using create_webhook. That means whenever something changes—like a meeting starting or ending—your system gets an immediate alert. When you need to know exactly who's in the room right now, you pull the list with list_participants. If you only care about one specific session, you can check out every person by calling list_participants on that single meeting.

Managing People and Content

Want to invite someone mid-call? You use add_participant to bring a specified user account directly into the active video conference. When your app's frontend client needs to connect, you can also get the necessary authentication tokens right there with these tools.

To keep track of what happens in these calls, if you need specifics on an existing meeting recording, you call get_recording and grab the download URL details. You'll find that running get_meeting often gives you context for what recordings are available too.

Live Streaming & Recording Management

You can start or stop a recording on an active meeting using start_recording and stop_recording. When you kick off the process, you even get to define storage parameters upfront—say, pointing it at your AWS S3 bucket. If you wanna broadcast the meeting to people who aren't in the room, you use start_livestream to make it public.

You shut down that public stream when you're done with stop_livestream. All these tools manage the state changes for you.

*You can even check on all your meetings and their status using list_meetings, which keeps everything clean and organized across your account. If you need to see exactly what recording details are available, remember that get_recording is the tool you'll use."