KinoPipe

io.github.nicolascoutureauPublished by GitHub account nicolascoutureauv1.0.1Updated Oct 24, 2026

FFmpeg as a service for AI agents: typed video editing tools, async jobs, downloadable outputs.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

KinoPipe gives an assistant hosted FFmpeg video editing tools, letting it run edits as async jobs and download the results.

What you can do
KinoPipe presents FFmpeg as a service for AI agents. It exposes typed video editing tools, runs editing work as asynchronous jobs, and makes the resulting outputs downloadable. The manifest does not list individual tool names.
When to use it
Use it when an assistant needs to perform video editing operations without running FFmpeg locally, and when asynchronous job handling with downloadable output files fits the workflow. It is a hosted service, so it suits users who are comfortable sending media to a remote endpoint.
Requirements
A remote streamable HTTP endpoint at kinopipe.com; no local package or runtime is needed. OAuth authentication is required. Network access to the endpoint is required.
Before you install
The server is a remote hosted service, so uploaded media and editing instructions are sent to a third party. Authentication is required via OAuth, granting the service access tied to your account. Review what happens to source files and rendered outputs before uploading private or sensitive footage.

Installation

In SourceWeft

  1. Open KinoPipe 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/io.github.nicolascoutureau%2Fkinopipe/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": {
    "kinopipe": {
      "type": "http",
      "url": "https://kinopipe.com/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.0.1LatestSep 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.