Dacast

Created By
Dacast-Inc6 months ago
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 Dacast’s broadcasting infrastructure through natural-language prompts in supported AI clients.
Overview

what is Dacast?

Dacast is a Model Context Protocol (MCP) Server that integrates Dacast’s video streaming and hosting platform with AI-powered applications, allowing users to manage video content through natural language prompts.

how to use Dacast?

To use Dacast, configure the MCP client with your Dacast API key and run the server. You can then manage channels, playlists, and other resources using natural language commands.

key features of Dacast?

  • StdIO-based MCP server for easy integration with AI clients.
  • Comprehensive Dacast API integration for managing channels, playlists, images, and simulcast destinations.
  • Supports natural language commands for resource management.

use cases of Dacast?

  1. Automating video content management for live events.
  2. Integrating video streaming capabilities into AI applications.
  3. Simplifying the management of video resources through natural language.

FAQ from Dacast?

  • What is required to use Dacast?

A Dacast account and API key are required for authenticated operations.

  • Can I manage live streams with Dacast?

Yes! Dacast allows you to control live streams and manage video content effectively.

  • Is there a specific programming language required to use Dacast?

Dacast is built with Go, and you need to have Go installed to run the server.

Server Config

{
  "mcpServers": {
    "dacast": {
      "command": "go",
      "args": [
        "run",
        "github.com/Dacast-Inc/mcp-server-public@latest"
      ],
      "env": {
        "DACAST_API_KEY": "DACAST API KEY HERE"
      }
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
Dacast-Inc
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago