Dacast

Name: Dacast
Author: Dacast-Inc

@Dacast-Inc

About Dacast

The Dacast MCP (Model Context Protocol) Server integrates Dacast’s comprehensive video streaming and hosting platform with your AI-powered applications. Once configured, you can upload and manage video content, control live streams, review analytics, and access nearly all of Daca

#dacast #video-streaming #ai-integration

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "dacast": {
      "command": "go",
      "args": [
        "run",
        "github.com/Dacast-Inc/mcp-server-public@latest"
      ],
      "env": {
        "DACAST_API_KEY": "DACAST API KEY HERE"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Dacast?

Dacast MCP Server is a Model Context Protocol server that exposes the Dacast video platform API as a set of structured MCP tools. It lets MCP-compatible clients manage Dacast resources like channels, playlists, images, and simulcast destinations through natural language.

How to use Dacast?

Install with Go 1.24+ and a Dacast account with API key. Configure your MCP client (e.g., Claude Desktop) with the JSON configuration provided, setting the DACAST_API_KEY environment variable. Launch as a child process via go run github.com/Dacast-Inc/mcp-server-public@latest.

Key features of Dacast

StdIO-based MCP server speaking the Model Context Protocol.
Channel management: create, list, get, update.
Playlist management: create, list, get, update, set content.
Image management: thumbnails and splash images.
Simulcast destination management: create, get, delete.

Use cases of Dacast

Create and update video channels from a chat interface.
Manage playlist content and structure without coding.
Set thumbnail or splash images for channels or assets.
Configure simulcast destinations for live streaming.

FAQ from Dacast

What runtime does Dacast MCP Server need?

Go 1.24+ is required; earlier versions may work but are not guaranteed.

How do I authenticate with Dacast?

You must provide a Dacast API key via the DACAST_API_KEY environment variable in the MCP client configuration.

What transport does the server use?

It uses StdIO (standard input/output) transport as an MCP server, designed to be launched and kept running as a child process by an MCP client.

Can I manage all Dacast resources through this server?

The server currently exposes tools for channels, playlists, images (thumbnails and splash), and simulcast destinations. Other Dacast resources are not mentioned.