How to Use the Dyte MCP in Claude Code

Q: How do I install the Dyte MCP Server for Claude Code?

Use the command claude mcp add --transport http -- . After running this, verify the connection with claude mcp list to ensure all tools are ready.

Q: Can Claude Code use Dyte to automate meeting creation in scripts?

Yes, you can trigger createmeeting within your shell scripts or cron jobs. Claude Code executes the tool and returns the result for your automated pipelines.

Q: Is it possible to stop Dyte recordings via Claude Code?

Absolutely. You can call stoprecording as part of your cleanup logic. The agent handles the request and confirms the recording has ended.

Deploy the Dyte MCP Server with Claude Code to automate video infrastructure from your terminal.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dyte MCP to Claude Code

Create your Vinkius account to connect Dyte to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Dyte with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Headless meeting orchestration for Claude Code

Run `create_meeting` directly from your shell to initialize sessions for your CI/CD pipelines. Claude Code handles the response data, allowing you to pipe the meeting ID into other scripts. This setup works for automated testing where you need to spawn rooms on the fly. The agent ensures each meeting is created with the correct parameters before moving to the next step.

Terminal-based stream control with MCP Server

Manage your recordings without a GUI by invoking `start_recording` through the CLI. Claude Code executes the command and returns the status of your media session. This is ideal for scheduled jobs that need to capture live events. The agent also handles `stop_recording` to finalize your assets, keeping your terminal workflow clean and efficient.

Query session logs using Claude Code

Get instant visibility into your meetings by calling `get_meeting` or `list_participants` from the command line. The output comes back as structured text ready for parsing. Use this to build automated alerts or reports based on live meeting status. Claude Code captures the tool output, letting you redirect the data to files or other processing tools.

Setup guide

Set up Dyte MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see dyte-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Dyte transactions." It will automatically discover and invoke the available Dyte tools.

Terminal

claude mcp add --transport http dyte-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Dyte MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "dyte-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dyte. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Dyte now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Dyte MCP in Claude Code

Use the command `claude mcp add --transport http -- `. After running this, verify the connection with `claude mcp list` to ensure all tools are ready.

Yes, you can trigger `create_meeting` within your shell scripts or cron jobs. Claude Code executes the tool and returns the result for your automated pipelines.

Absolutely. You can call `stop_recording` as part of your cleanup logic. The agent handles the request and confirms the recording has ended.

The server supports http, sse, and stdio transports. You specify your choice during the initial `claude mcp add` command.

The server functions as a stateless bridge, passing meeting IDs and participant tokens to the API. It does not store your session logs, and all communication is encrypted.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript