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.

Cursor connector (MCP)

Build live streaming, video hosting and embeddable players into the sites and platforms you write in Cursor. The DCAST connector is a remote MCP server at https://api.dcast.pro/mcp: Cursor's agent works on your own DCAST account with the access you grant, creates streams and uploads, takes embed codes from DCAST and can find and call any documented Partner API operation while it writes your integration. DCAST hosts, transcodes and delivers the video you send it; it does not generate video. Payments are never available.

What you need

  • A DCAST account at dcast.pro. Every plan can connect, including the free one. What the agent can do follows your plan exactly as on the website and in the API: storage, streaming hours and features.
  • Cursor on your computer.

Add to Cursor in one click

Add DCAST to Cursor

  1. Open the link above on the computer where Cursor is installed. Cursor asks whether to install the dcast server; confirm.
  2. When Cursor asks you to sign in, it opens the DCAST sign-in page (on dcast.tv or dcast.pro, depending on your account). Sign in and choose the access you grant (see Authorization below). You do not enter a client ID or a client secret: Cursor registers itself with DCAST automatically.
  3. Cursor's agent can now use the DCAST tools. Ask it, for example, to put a live player on your site.

Once DCAST is listed in the Cursor Marketplace, you can also install it from Customize → MCPs in Cursor.

Add it by hand (mcp.json)

Put the server into ~/.cursor/mcp.json to use it in all your projects, or into .cursor/mcp.json inside one project to share it with your team through the repository. Sign-in then works as in the steps above.

{
  "mcpServers": {
    "dcast": {
      "url": "https://api.dcast.pro/mcp"
    }
  }
}

With an API key instead of signing in

You can also connect 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. Keep the key in the environment variable DCAST_API_KEY, as below, and never write it into the file or the repository.

{
  "mcpServers": {
    "dcast": {
      "url": "https://api.dcast.pro/mcp",
      "headers": {
        "Authorization": "Bearer ${env:DCAST_API_KEY}"
      }
    }
  }
}

Authorization

Sign-in uses OAuth 2.0 with PKCE through DCAST's own sign-in page. You choose how much to allow, and Cursor 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.

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

The DCAST rule for Cursor

A Cursor rule tells the agent how to build with DCAST: start from a recipe, look facts up in the DCAST documentation instead of guessing, put players on a page only as the embed tools return them, keep API keys and stream keys out of code, and delete nothing without your confirmation.

Add the DCAST rule to Cursor: Cursor shows the rule and adds it after you confirm.

Tools

Cursor gets the same tools as the Claude connector: named tools for the common jobs (videos, uploads, embed codes, live streams, multistreams, rooms, playlists, statistics) and tools that find, describe and call every other documented Partner API operation. Cursor asks for your approval before it runs a tool, unless you allowed that tool to run on its own.

If Cursor warns that too many tools are turned on, turn off the room and playlist tools you do not need in Cursor's tool list: dcast_find_operation and dcast_call_operation reach the same operations.

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.

Example requests

  • "Add a live player and chat for my DCAST stream to the event page."
  • "Upload intro.mp4 to DCAST and put the video on the landing page."
  • "Write a webhook endpoint that marks a lesson as ready when its DCAST video has finished processing."
  • "Create a password-protected stream for our employees and show it on the intranet page."

What is sent

When Cursor's agent 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 or your code is sent. Video files never go through the connector: an upload goes 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 Cursor is handled by Cursor 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).

Cursor connector (MCP) — dcast.pro API docs