English Français العربية

Longwave

السجل الرسمي التسويق والمبيعات

Give AI agents a creator's video pipeline: Shorts, thumbnails and YouTube publishing.

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http longwave 'https://www.longwave.media/api/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "longwave": {
            "type": "http",
            "url": "https://www.longwave.media/api/mcp"
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Longwave — the video pipeline for AI agents
  2. What it produces
  3. Why this exists
  4. Install
  5. Connect
  6. Tools
  7. What it costs
  8. Where it publishes
  9. Package layout
  10. Who maintains this
  11. Privacy and data
  12. Support
  13. License

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:

  • 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 episode's own transcript, not grabbed from a frame.
  • Transcript-based metadata — titles, descriptions, chapters, show notes and per-platform post copy, written for each destination.
  • An X post and an X video supercut — the link post and the native video clip are separate outputs, and both can run from the same episode.
  • A podcast RSS feed, built and syndicated to 13 directories — Apple Podcasts, Spotify, Amazon Music, iHeartRadio, Pocket Casts, Castbox and more.
  • 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.

Create and inspect — granted on first connect

ToolDoes
account_statusChannel connected? Credits left? Call this first.
create_shorts_jobCut a long-form episode into Shorts. Free — credits are spent on publish.
get_jobProgress, clip count and errors for a job.
list_clipsWhat was produced, with per-platform status and live URLs.
create_supercutAssemble one longer cut from a source video or from existing clips.

Read — granted on first connect

ToolDoes
list_episodesThe creator's long-form catalogue, newest first, with status.
get_episodeOne episode in full: titles, notes, chapters, transcript, podcast state.
get_insightsChannel-level summary: episode counts, recurring topics, hook types.
get_content_intelligenceLongwave's written analysis of what to make next.
get_channel_overviewConnected platforms and how each is performing.
list_playlistsPlaylists, and which one is the upload destination.
list_thumbnail_stylesThe thumbnail style catalogue.

Change something public — a separate approval, every time

ToolDoes
publish_shortsPublish Shorts to YouTube, with scheduling.
reschedule_postMove a queued post to a different hour, or unschedule it.
approve_thumbnailPublish 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.

What it costs

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.

ActionCredits
Publish a Short1
Publish a Short on autopilot1.5
Publish to X through the shared app quota4
Upload a full long-form episode5, 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.

Where it publishes

  • Through the official API, by Longwave — YouTube (the episode and its Shorts), X (a post and a supercut), a public Link-in-Bio hub, and podcast RSS syndicated to 13 directories.
  • As a downloadable file — every Short is a vertical file on the CDN with its caption and metadata attached, so an agent can post it anywhere from the creator's own signed-in session.

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.

Package layout

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:

PathConvention
plugin.jsonAgent Plugins v1.0.0 — closed schema, fixed location
mcp.jsonAgent Plugins v1.0.0 — transport streamable-http
.grok-plugin/plugin.jsonGrok / xAI marketplace — verified against xAI's own vendored external_plugins/neon and third-party getsentry/plugin-grok
.mcp.jsonGrok MCP config — transport http
skills/longwave/SKILL.mdShared by both — the instructions the model reads
.grok-plugin/marketplace.jsonSelf-hosted catalog (tracks repo HEAD)
assets/logo.svgListing logo — the Groundswell mark, monochrome currentColor per brand canon
assets/icon.svg1: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

Who maintains this

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.

Submitting to the official xAI catalog

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.

Submitting to the Cursor Marketplace (this is Grok Bot's plugin catalog)

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.

Privacy and data

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

support@longwave.media · https://www.longwave.media · org profile

License

MIT for this package. That does not cover the hosted Longwave service.

الأسئلة الشائعة

ما هو Longwave؟

Give AI agents a creator's video pipeline: Shorts, thumbnails and YouTube publishing.

كيف أثبّت Longwave؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http longwave 'https://www.longwave.media/api/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Longwave إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل Longwave مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Longwave؟

ينشره Longwave-Media. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.