Public MCP Server

This repository provides a **Model Context Protocol (MCP) server** that exposes the Dacast video platform API as a set of structured MCP tools. It

Local serverstdioGo

What is the Public MCP server?

Public MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This repository provides a Model Context Protocol (MCP) server that exposes the Dacast video platform API as a set of structured MCP tools. It lets MCP-compatible clients (such as Claude Desktop) manage Dacast resources — channels.

What you get

  • StdIO-based MCP server —
  • Speaks the Model Context Protocol over standard input/output
  • Designed to be launched by an MCP client process and kept running as a child process
  • Dacast API integration —
  • Channel management: create, list, get, update
  • Playlist management: create, list, get, update, set playlist content

What the assistant can call

Once Public is connected, these are the calls the assistant has available:

  • create_channel.go — create a new channel
  • get_channel.go — get channel details
  • update_channel.go — update an existing channel
  • list_channel.go — list all or filtered channels
  • create_playlist.go — create a new playlist
  • get_playlist.go — get playlist details
  • update_playlist.go — update an existing playlist
  • list_playlist.go — list playlists
  • set_playlist_content.go — set or update playlist content
  • thumbnail.go — manage channel/asset thumbnails
  • splash.go — manage splash images
  • create_simulcast_destination.go — create a simulcast destination

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need one environment variable: DACAST_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Go: Go 1.24+ (earlier versions may work but are not guaranteed). - Dacast account and API key: required to perform authenticated operations.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Public's toolset — create_channel.go, get_channel.go, update_channel.go and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dacast-inc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Public.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the public mcp server does with a few real requests.

Available tools

ToolWhat it does
create_channel.gocreate a new channel.
get_channel.goget channel details.
update_channel.goupdate an existing channel.
list_channel.golist all or filtered channels.
create_playlist.gocreate a new playlist.
get_playlist.goget playlist details.
update_playlist.goupdate an existing playlist.
list_playlist.golist playlists.
set_playlist_content.goset or update playlist content.
thumbnail.gomanage channel/asset thumbnails.
splash.gomanage splash images.
create_simulcast_destination.gocreate a simulcast destination.
get_simulcast_destination.goretrieve a simulcast destination.
delete_simulcast_destination.godelete a simulcast destination.

How to install the Public MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Go: Go 1.24+ (earlier versions may work but are not guaranteed). - Dacast account and API key: required to perform authenticated operations.
VariableDescriptionRequired
DACAST_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Public to create channel.go.
  • Use Public to get channel.go.
  • Use Public to update channel.go.

Frequently asked questions

It connects Public to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (create_channel.go, get_channel.go, update_channel.go, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Public directly.