MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Give AI agents a creator's video pipeline: Shorts, thumbnails and YouTube publishing.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://www.longwave.media/api/mcpRun this in your terminal
claude mcp add --transport http longwave https://www.longwave.media/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"longwave": {
"url": "https://www.longwave.media/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"longwave": {
"type": "http",
"url": "https://www.longwave.media/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://www.longwave.media/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain longwave.media (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 38 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Point Longwave at one long-form episode, podcast or YouTube video and a whole distribution stack comes back:
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.
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.
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.
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.
https://www.longwave.media/api/mcp (Streamable HTTP, stateless)https://www.longwave.media/.well-known/oauth-protected-resourcehttps://www.longwave.media/.well-known/oauth-authorization-serverFifteen 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.
Create and inspect — granted on first connect
| Tool | Does |
|---|---|
account_status | Channel connected? Credits left? Call this first. |
create_shorts_job | Cut a long-form episode into Shorts. Free — credits are spent on publish. |
get_job | Progress, clip count and errors for a job. |
list_clips | What was produced, with per-platform status and live URLs. |
create_supercut | Assemble one longer cut from a source video or from existing clips. |
Read — granted on first connect
| Tool | Does |
|---|---|
list_episodes | The creator's long-form catalogue, newest first, with status. |
get_episode | One episode in full: titles, notes, chapters, transcript, podcast state. |
get_insights | Channel-level summary: episode counts, recurring topics, hook types. |
get_content_intelligence | Longwave's written analysis of what to make next. |
get_channel_overview | Connected platforms and how each is performing. |
list_playlists | Playlists, and which one is the upload destination. |
list_thumbnail_styles | The thumbnail style catalogue. |
Change something public — a separate approval, every time
| Tool | Does |
|---|---|
publish_shorts | Publish Shorts to YouTube, with scheduling. |
reschedule_post | Move a queued post to a different hour, or unschedule it. |
approve_thumbnail | Publish an AI-generated thumbnail on the episode. |
Publishing and thumbnail changes are not granted on first connect — they are a step-up the creator approves separately, because both change something public. The server asks for the extra permission with 403 + WWW-Authenticate: ... error="insufficient_scope".
tools/list returns the whole catalogue regardless of grant, so a client can see what exists and ask for it; the grant is enforced on the call. `tools/list` is authoritative and carries each tool's full JSON Schema — the tables above are for someone reading this repo.
Every mutating tool accepts an idempotency_key. Retry a timed-out call with the same key and you get the original result rather than a second job or a second public post.
The creator starts free: 200 credits on signup, no card, and they do not expire.
Credits are charged to the creator per Short that actually publishes — nothing for a failed render, nothing for a clip that is never posted.
| Action | Credits |
|---|---|
| Publish a Short | 1 |
| Publish a Short on autopilot | 1.5 |
| Publish to X through the shared app quota | 4 |
| Upload a full long-form episode | 5, plus 1 per GB |
The agent never handles payment. It holds no card and cannot reach a checkout. When the balance runs low a tool returns a top_up_url; the agent's job is to hand it to the creator and stop.
Longwave is not a party to any third-party platform's terms and never contacts them. We describe the capability; the creator's agent performs the action.
Two ecosystems describe plugin packages differently, and a client that finds no MCP config installs a plugin with zero tools. Both layouts are therefore shipped:
| Path | Convention |
|---|---|
plugin.json | Agent Plugins v1.0.0 — closed schema, fixed location |
mcp.json | Agent Plugins v1.0.0 — transport streamable-http |
.grok-plugin/plugin.json | Grok / xAI marketplace — verified against xAI's own vendored external_plugins/neon and third-party getsentry/plugin-grok |
.mcp.json | Grok MCP config — transport http |
skills/longwave/SKILL.md | Shared by both — the instructions the model reads |
.grok-plugin/marketplace.json | Self-hosted catalog (tracks repo HEAD) |
assets/logo.svg | Listing logo — the Groundswell mark, monochrome currentColor per brand canon |
assets/icon.svg | 1:1 marketplace logotype — Groundswell on the ink plate, full-bleed 1024. This is the one a listing tile wants, because a monochrome mark with no plate disappears on a light or busy background |
Longwave is a product of Signal Group Limited (New Zealand · NZBN 9429035771678 · Co. No 1396666). The dashboard repo's scripts/verify-plugin-package.ts validates this package before any release — 58 checks covering both manifest conventions, author agreement, a single MCP endpoint across both configs, and drift between the skill's allowed-tools, this README and the live tool manifest.
Entries live in xai-org/plugin-marketplace, where the source must be SHA-pinned to a full 40-character lowercase commit — scripts/validate-catalog.py enforces that, and Grok re-verifies git rev-parse HEAD == sha after cloning, so a force-push cannot silently ship new code. xAI also expects the source to be an organisation repository; ours is Longwave-Media.
git ls-remote https://github.com/Longwave-Media/longwave-plugin.git HEAD
Then add the entry, regenerate the component index, validate, and open a PR:
python3 scripts/generate-plugin-index.py
python3 scripts/validate-catalog.py
Re-pin `sha` on every release — never open a parallel entry.
Grok Bot installs its plugins — Settings → Plugins — from the Cursor Marketplace, which is a different surface from Grok Build's catalog above. Submission is a form, not a pull request: paste this repository's URL at https://cursor.com/marketplace/publish. The Cursor team manually reviews a new listing and every update, so there is no SHA pin to maintain — the listing tracks the default branch.
This package is already in the format Cursor accepts: a root plugin.json per the Agent Plugins specification, with mcp.json, skills/ and README.md alongside it. keywords and the description are what a marketplace search matches, which is why the manifest carries the plain words a creator would type — youtube, shorts, reels, video, clips, podcast — and not just the product vocabulary.
This package collects nothing and stores nothing. Anything the creator acts on is handled by the hosted Longwave service under its own terms: https://www.longwave.media/terms and https://www.longwave.media/privacy. YouTube credentials never leave Longwave's servers, and the agent receives only an opaque, scoped Longwave token.
support@longwave.media · https://www.longwave.media · org profile
MIT for this package. That does not cover the hosted Longwave service.