An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Dyte to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run meetings and livestreams through your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 11 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 11 available through Dyte.

  1. 01

    Create meeting

    This capability starts a new Dyte meeting immediately.

  2. 02

    Create webhook

    Use this to set up real-time event notifications for your backend.

  3. 03

    Start livestream

    This capability begins a livestream for an active meeting.

  4. 04

    Stop livestream

    Use this to end a meeting's active livestream.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 11 available through Dyte.

  1. 05

    Stop recording

    This capability stops a recording that is currently running.

  2. 06

    Get meeting

    This capability fetches specific details about a meeting.

  3. 07

    Add participant

    Use this to add a user to a meeting and get their auth token.

  4. 08

    Get recording

    This capability retrieves details and download info for a recording.

Capability set03 / 03

09-11

3 capabilities in this set.

Part of 11 available through Dyte.

  1. 09

    List meetings

    This capability returns a list of all your existing meetings.

  2. 10

    List participants

    Use this to see everyone currently in a meeting.

  3. 11

    Start recording

    This capability starts a meeting recording with optional storage settings.

Real work

What teams actually run

01

Automated Webinar Setup

An operations team uses the AI to create meetings and add speakers automatically.

02

Rapid Prototyping

Developers test video call features by commanding the AI to spin up rooms.

03

Meeting Monitoring

Product managers check participant lists and recording status via their AI client.

04

Live Event Management

Teams start and stop livestreams for large audiences using simple text commands.

Automate a task

Put Dyte to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Dyte works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Dyte to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1002ms average. Fast in production.

Dyte is checked daily against the live service.

Daily averagePeak 1196ms
Oct 3Today
Fastest day
777ms
Slowest day
1196ms
14-day trend
Slowing+17%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 11 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Dyte, so you can see the experience inside your AI.

It does not authenticate your account with Dyte. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Dyte Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_1FuAxqsgOTP3wlR6HEGsoXdZYF2SJrn4e2OmQkoI/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Dyte capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "dyte-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_1FuAxqsgOTP3wlR6HEGsoXdZYF2SJrn4e2OmQkoI/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Dyte in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Dyte owners hand off.

This MCP is built for technical teams who need to automate or manage video workflows without constant manual intervention.

  • 01

    Developers

    They use the AI to test video workflows without writing boilerplate code.

  • 02

    Product Managers

    They monitor active meetings and manage recording assets through chat.

  • 03

    Operations Teams

    They automate participant access for webinars and internal calls.

FAQ

Questions Dyte owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the Dyte MCP on Vinkius and enter your Dyte credentials. Once connected, you can immediately use it in Claude, Cursor, Windsurf, or other compatible clients.

  • 02

    What credentials do I need?

    You will need your Dyte Organization ID and your API Key to authenticate the connection.

  • 03

    Can I use this to manage recordings?

    Yes, you can start and stop recordings and use the capability to fetch download URLs for your recorded content.

  • 04

    Does this MCP handle participant authentication?

    Yes, the AI can add participants to meetings and generate the specific auth tokens required for your frontend SDKs.

  • 05

    Can I livestream my meetings?

    Yes, you can use the livestreaming capabilities to start or stop broadcasts for your meetings.

  • 06

    How do I get the authentication token for a new participant to join a meeting?

    Use the add_participant capability. You need to provide the meeting_id, name, and a preset_name. The capability will return the authToken required by Dyte's frontend SDKs.

  • 07

    Can I configure where my meeting recordings are stored?

    Yes. When using the start_recording capability, you can optionally provide a storage_config JSON object (e.g., for AWS S3) to define your custom storage destination.

  • 08

    How can I monitor when a meeting starts or ends in real-time?

    You can use the create_webhook capability to register a URL that Dyte will notify when specific events occur, such as meeting.started or meeting.ended.

Explore

More in Developer Tools

Suggestions

Connect Dyte to Claude, Cursor, ChatGPT & more