Longwave MCP server

Longwave — the video pipeline for AI agents

Give any AI agent a creator's whole video pipeline. Turn one long-form episode into Shorts, thumbnails, show notes and a podcast feed — then publish to the creator's own YouTube channel.

Works with Grok Bot, Grok Build, Cursor, Claude Code and Meta Muse. One MCP connection, OAuth 2.1, and no API key anywhere.

Agents orchestrate. Longwave renders and publishes. The agent never downloads video, never holds Google credentials, and never drives YouTube Studio.

What it produces

Point Longwave at one long-form episode, podcast or YouTube video and a whole distribution stack comes back:

episode's own transcript, not grabbed from a frame.

• Captioned vertical Shorts and clips — cut, framed and captioned from the transcript.
• Contextual AI thumbnails — the hook, the subtitle and the scene are generated from the

copy, written for each destination.

• Transcript-based metadata — titles, descriptions, chapters, show notes and per-platform post

outputs, and both can run from the same episode.

• An X post and an X video supercut — the link post and the native video clip are separate

Music, iHeartRadio, Pocket Casts, Castbox and more.

• A podcast RSS feed, built and syndicated to 13 directories — Apple Podcasts, Spotify, Amazon

• A public link-in-bio hub for the creator's channel.

YouTube and X publish automatically. Every other clip is rendered as a captioned vertical file ready to drop into Reels, TikTok and LinkedIn. Longwave is not a party to those platforms' terms and never contacts them; the creator's own agent performs that step from the creator's session.

Why this exists

An agent can already cut video and drive a browser. Two things it cannot get for itself:

1. A verified YouTube upload grant. Google approved Longwave for youtube.force-ssl — production mode, no user cap, no "unverified app" screen. The creator connects once, and Longwave delegates scoped access to the agent. Standing up your own integration means OAuth app review and Google verification before the first upload.

2. A pipeline, not a command. Cutting a Short is the easy part. Longwave also does the captions, the title and description, the thumbnail, the playlist routing, the daily upload caps, the cross-platform schedule, the podcast RSS feed and the retry when an upload fails halfway.

So this is not a wrapper around yt-dlp and a Studio bookmarklet. It is the publishing authority, exposed as fifteen tools.

Install

grok plugin install Longwave-Media/longwave-plugin

Or add it as a self-hosted catalog source:

grok plugin marketplace add Longwave-Media/longwave-plugin

Both work with no review. Cursor and Claude Code read the same files; Muse builds its own MCP client from the URL.

Connect

Nothing to configure, and no credentials live in this repo. An unauthenticated call to the MCP endpoint returns:

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer resource_metadata="https://www.longwave.media/.well-known/oauth-protected-resource"

A conformant client follows that, registers itself, opens a browser, and the creator signs in and approves. PKCE S256 is required. This is deliberate: Agent Plugins v1.0.0 §7.2.1 forbids embedding secrets in headers, and OAuth discovery is how the spec expects authorization to work.

• MCP endpoint — https://www.longwave.media/api/mcp (Streamable HTTP, stateless)
• Protected-resource metadata — https://www.longwave.media/.well-known/oauth-protected-resource
• Authorization server — https://www.longwave.media/.well-known/oauth-authorization-server

Tools

Fifteen tools — enough to run a creator's clip pipeline end to end, and deliberately no more. The surface is a deny-by-default allowlist, not a mirror of the API, so a tool exists here because it has an ownership-checked backing route.

Shortened. The full README is on GitHub.