Partner API base path is /api/v1 on https://api.dcast.pro. This site documents the live surface; use the Quickstart QA curls to validate keys and routes.

Claude connector (MCP)

The DCAST connector lets you run live streams, multistream to YouTube, Twitch and Facebook, and publish videos on DCAST from a conversation in Claude. DCAST hosts, transcodes and delivers the video you send it; it does not generate video. The connector is a remote MCP server at https://api.dcast.pro/mcp that works on your own DCAST account with the access you grant. Besides its named tools it can find and call any documented Partner API operation within that access; payments are never available.

What you need

  • A DCAST account at dcast.pro. Every plan can connect, including the free one. What you can do follows your plan exactly as on the website and in the API: storage, streaming hours and features. Ask Claude "how much storage do I have left?" to see the allowance.
  • Claude on the web, desktop or mobile, or Claude Code.

Connect in Claude

  1. Open Settings → Connectors in Claude and choose Add custom connector.
  2. Enter the server URL https://api.dcast.pro/mcp.
  3. Choose Add, then Connect. You do not enter a client ID or a client secret: Claude registers itself with DCAST automatically.
  4. Claude opens the DCAST sign-in page (on dcast.tv or dcast.pro, depending on your account).
  5. Sign in and choose the access you grant (see Authorization below). Claude can now use the tools.

Once the connector is listed in the Claude connector directory, you add it from the directory and skip steps 1 and 2.

Claude Code

Claude Code connects with a DCAST Partner API key that you create in your DCAST account under API keys. The key's own access level (read only, standard, full) applies. Do not paste the key into a chat.

claude mcp add --transport http dcast https://api.dcast.pro/mcp --header "Authorization: Bearer <your key>"

Or sign in with your DCAST account instead of a key: add the server with the command below (no client ID is needed: Claude Code registers itself), then run /mcp in Claude Code and choose Authenticate. Claude Code opens the DCAST sign-in page, as in the steps above.

claude mcp add --transport http dcast https://api.dcast.pro/mcp

Authorization

Sign-in uses OAuth 2.0 with PKCE through DCAST's own sign-in page. You choose how much to allow, and Claude never sees your password:

  • Read (dcast:read): see your DCAST videos, live streams, multistreams, rooms, playlists, webhooks and statistics.
  • Write (dcast:write): create and change videos, live streams, multistreams and playlists.
  • Delete (dcast:delete, optional): delete videos, live streams, multistreams and playlists.

There are no payment tools: the connector cannot see or change billing, payouts, sales or payment methods, cannot create API keys and cannot give other people access to your account. It has no tool that sends an arbitrary request: dcast_call_operation calls only operations published in the OpenAPI document and checks the arguments against it before anything is sent. Every call is one Partner API call made with your own access, so it can do only what your account and the granted access allow.

To disconnect, disable the key named Claude connector (OAuth) in your DCAST API keys. Claude then gets no further access.

Rules for the agent

They tell the agent how to use the DCAST tools and how to put a player on a page so that it looks right: the embed code exactly as the tool returns it, poster images in a list and one player on the page. Claude receives these rules from the connector itself, together with every embed code. In Claude Code you can also put this text into CLAUDE.md in the root of your project.

# Working with DCAST

DCAST hosts, transcodes and delivers video and live streams for the connected DCAST account. It does not generate video.
The `dcast` MCP server works on that account with the access the user granted.

## Before writing code

- Call `dcast_get_recipe` first (no argument lists the recipes). Follow a recipe's steps in order.
- Call `dcast_search_docs` for anything you are about to rely on: fields, limits, plans, errors, webhooks. Use only what it returns; never invent endpoints, fields, embed markup or limits.
- For any operation without a named tool: `dcast_find_operation` to find it, `dcast_describe_operation` for the exact request, then `dcast_read_operation` (GET), `dcast_call_operation` (POST/PUT/PATCH) or `dcast_delete_operation` (DELETE).
- When you write integration code, take the method, path, fields and headers from `dcast_describe_operation`. The Partner API base is `https://api.dcast.pro/api/v1`.

## Embed codes and addresses

- Players and chat go on a page only as returned by `get_stream_embed_codes` or `get_video_embed_code`. Never write your own iframe, player URL or ingest address.
- Ids, playback links and ingest addresses always come from a tool answer.

## Putting a player on a page

- Paste the code exactly as returned. Use `responsive` (it fills its container's width in the video's shape); `iframe` only for one fixed pixel size (set by width/height).
- The chat skin is asked for, not edited in: on a dark website call get_stream_embed_codes with `theme` `dark` (or `auto`) and paste that answer; never add `?theme=` by hand.
- Never wrap the player in your own frame, border, rounded or fixed-height box, nor set width, height, border-radius or object-fit on the iframe: that cuts off the picture or the controls.
- For a smaller player put `responsive` into a narrower container (e.g. `max-width: 480px`), never a fixed height.
- Several videos on a page: show posters (`thumbnailUrl` from list_videos or get_video) with titles and load the player only for the clicked video: one player on the page, above the list or in a dialog.
- Every embedded player starts playing by itself, muted, once loaded, so never put several player iframes in a grid or list.
- Titles, descriptions and posters come from the API; never invent them.

## Secrets

- A DCAST Partner API key (`pk_...`) is a server-side secret. Read it from an environment variable in server code. A website gets its key from the DCAST site connector: call `ask_site_access` (recipe `website-with-my-videos`); the user clicks Allow and the key lands in the site's environment. Never ask the user to create, copy or paste a key. Never put it in browser code, in a repository, in `mcp.json` as plain text or in a chat answer.
- Stream keys are secret. Call `reveal_stream_key` only when the user asks for the encoder key, and never write a stream key into code or a file.

## Changes and deletes

- Look with `list_*` / `get_*` tools. Create or change only what the user asked for.
- Call `delete_*` tools and `dcast_delete_operation` only after the user confirms; a delete cannot be undone.

## Uploads

- `create_video_upload` returns an upload link; the file bytes go from the user's machine or server straight to that link, never through the chat. `import_video_from_url` takes a direct file link.
- Follow processing with `get_video_status` no more often than every 10 seconds.

## Errors and plan limits

- An error answer carries `code`, `message` and `howToFix`; do what `howToFix` says.
- The errors an operation can answer are listed in `dcast_describe_operation` (`errors`) and every error answer carries `howToFix`: do what it says; no need to look the error up on the website.
- A plan limit names the limit: ask `dcast_search_docs` which plan raises it and tell the user. Do not retry the same call.

Tools

The connector has a core of named tools (table below) and five tools that reach every other documented operation. Read tools run without confirmation; Claude asks you before anything that changes your account, and always before a delete.

ToolTypeWhat it does
get_accountReadThe connected account: plan, granted access and permissions, number of videos and live streams.
list_videosReadVideos, newest first; filter by processing status, visibility or a search phrase.
get_videoReadOne video: title, description, visibility, duration, resolution, status and playback links.
get_video_statusReadUpload and processing progress of a video.
get_import_statusReadStatus of a video import started from a link.
get_video_embed_codeReadHTML iframe embed code and URL of a video.
list_streamsReadLive stream cards with live or offline state and viewers. Stream keys are hidden.
get_streamReadOne live stream card: protocol, ingest addresses (RTMP, SRT, WHIP), playback links, state.
get_stream_statusReadWhether a stream is live, whether the encoder signal arrives, current viewers.
reveal_stream_keyReadThe secret stream key and full ingest URLs of one stream. Called only when you ask for the key.
get_account_analyticsReadViews, storage use and content counts over a period.
get_storage_quotaReadStorage used and the storage allowance of your plan, with the quota state.
list_restreamsReadMultistream setups that forward a DCAST stream to other platforms. Destination keys are hidden.
get_stream_embed_codesReadReady HTML to embed the player and the chat of a stream on your site.
get_embed_domainsReadThe sites allowed to embed your player.
dcast_search_docsReadSearch these docs; answers quote the page word for word with a link.
dcast_get_recipeReadStep-by-step recipe for a common job (see Recipes below).
dcast_find_operationReadFind the API operation for a job in a few words.
dcast_describe_operationReadThe exact request of one operation, from the OpenAPI document: fields, required fields, allowed values.
dcast_read_operationReadCall one documented read operation (GET) after checking the arguments against its contract. It only reads and changes nothing.
import_video_from_urlWriteCreate a video by importing it from a public file link; DCAST downloads, stores and transcodes it.
create_video_uploadWriteCreate a video card and a one-time upload link. The file itself goes from your computer to that link, not through Claude.
update_videoWriteChange the title, description or visibility of a video. Claude asks you to confirm first.
create_streamWriteCreate a live stream card and get RTMP, SRT or WHIP (browser) ingest addresses.
start_streamWritePress Start on a stream whose encoder is already sending, so viewers get the broadcast.
end_streamWriteStop the live broadcast for viewers. The stream card stays and can be used again; Claude asks you to confirm first.
create_restreamWriteForward one of your streams to YouTube, Twitch, Facebook or a custom RTMP server.
update_streamWriteChange the title, description, access or price of a live stream. Claude asks you to confirm first.
set_embed_domainsWriteChange the sites allowed to embed your player. Claude asks you to confirm first.
dcast_call_operationWriteCall one documented operation that creates or changes data (POST, PUT, PATCH) after checking the arguments against its contract. Claude asks you to confirm first. A delete goes only through dcast_delete_operation.
delete_videoDeletePermanently delete a video with its files. Needs the delete access; Claude asks you to confirm first.
delete_streamDeleteDelete a live stream card. Needs the delete access; Claude asks you to confirm first.
dcast_delete_operationDeleteCall one documented delete operation (DELETE) after checking the arguments against its contract. Claude asks you to confirm first; it needs the delete access.

Stream keys are hidden in every answer. Claude shows one only through reveal_stream_key, and only for your own stream, when you ask for it.

Never available through the connector: payments, payouts and sales, creating or revoking API keys, adding or removing team members, file uploads through the chat (the file goes from your computer to the upload link), live event streams (Claude checks the status instead) and actions meant for viewers, such as likes and poll votes.

Recipes

Ask Claude for one of these and it follows the recipe step by step:

  • Put a live player and chat on your website.
  • A private broadcast for employees, with a password or sign-in.
  • A company radio station on your website.
  • Multistream to YouTube, Twitch and Facebook.
  • Sell access to a broadcast or a video.
  • Upload or import a video and get its embed code.
  • Get notified by webhook, or check the status, when a broadcast starts or a video is ready.

Example requests

  • "Create a live stream called Friday Q&A and give me the OBS settings."
  • "Is my stream live right now, and how many people are watching?"
  • "Start broadcasting my stream Friday Q&A to viewers, then end it when I say so."
  • "Forward my stream Friday Q&A to YouTube and Twitch."
  • "Import this video from https://example.com/demo.mp4 and tell me when it is ready."
  • "Make my video Product tour private and give me its embed code."
  • "How many views did I get last month and how much storage is left?"
  • "Create a poll in my room Weekly sync: Which day works best?"
  • "Create a playlist called Webinars and add my three latest videos to it."

What is sent

When Claude calls a tool, the tool's arguments (for example a video title or a stream id) and your access token are sent to https://api.dcast.pro/mcp, which passes them to the DCAST Partner API. Nothing else from your conversation is sent. Video files never go through Claude: an upload goes from your computer straight to the upload link DCAST gives, and an import is downloaded by DCAST from the link you provide.

Privacy

DCAST's privacy policy: https://dcast.pro/privacy. Your conversation with Claude is handled by Anthropic under its own privacy policy.

Support

Write to [email protected]. The REST API behind the connector is documented in the Partner API reference; its limits and error codes apply to the connector too (see Errors and limits).

License

The connector and the DCAST plugin for Claude are released under the MIT license.