Open Video

video.openPublished by open.videoOfficial publisherv1.6.0Updated Oct 25, 2026

AI-powered video publishing, channel management, and monetization via open.video

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Open Video is a remote MCP server that lets an assistant publish videos, manage channels and handle monetization on open.video.

What you can do
Publish and manage video content on open.video through the assistant, using AI-assisted publishing workflows. Manage channels on the platform. Handle monetization-related tasks for published content. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when you publish video on open.video and want an assistant to handle uploads, channel upkeep or monetization tasks without switching to the platform's own interface.
Requirements
A remote MCP endpoint at mcp.open.video over streamable HTTP. OAuth authentication is required, so you need an open.video account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your open.video account and can act on your behalf, including publishing content, changing channels and monetization settings. Review what the OAuth grant permits before connecting, and confirm any publish, edit or monetization action before it runs.

Installation

In SourceWeft

  1. Open Open Video in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/video.open%2Fopen-video/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "open-video": {
      "type": "http",
      "url": "https://mcp.open.video/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.6.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.