Media · Remote MCP server
Clipwave
Generate video and images, edit them on a real multi-track timeline, and export an MP4.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.clipwave/clipwave- Version
- 0.1.0
- Status
- Active
- Category
- media
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- io.clipwave
- Namespace
- Namespace verified by the MCP Registry via the domain clipwave.io · how
- Website
- clipwave.io/mcp
- Repository
- github.com/ClipWave-io/clipwave-plugins
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://clipwave.io/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Clipwave
Clipwave is a remote MCP server: there is nothing to install. Its endpoint is https://clipwave.io/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More media servers
| Server | Runs |
|---|---|
| ClippyAI agents can Create rooms and store/retrieve text and images, and hand link to humans no sign-up. | Remote · HTTPLive check: ✓ handshake |
| Clipspeed MCPTurn any video or livestream into scored, captioned, ready-to-post vertical clips. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ClipTalkCreate and edit social videos from chat: script, AI visuals, voiceover, captions, music, MP4. | Remote · HTTPLive check: sign-in required |
| ClipUGCUGC videos for your app with AI influencers who keep the same face. Hosted (OAuth) or local. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ClipwiseMCP server for Clipwise - AI tools for TikTok, Reels, and Shorts video creators. | Local · stdio |
| ClipwrightTalking-actor and faceless short videos from your AI agent, with a free quote before each render. | Local · stdio |
| Clipzyn MCPTurn podcasts and long videos into ranked, finished short clips via the hosted ClipZyn API. | Remote · HTTPLive check: sign-in required |
| Cloud Api Hub Youtube DownloaderCloud Api Hub - Youtube Downloader: Get Youtube video info and download links to MP4 or MP3 file. | Remote · HTTPLive check: ✓ handshake |