
CaptionPipe
com.captionpipePublished by captionpipe.comOfficial publisherv1.0.0Updated Oct 24, 2026
One call burns captions into your video. Hosted, prepaid, no subscription. MP4 plus SRT and VTT.
Overview
Burns caption files into a video, returning a captioned MP4 from an uploaded video plus SRT or VTT subtitles.
- What you can do
- CaptionPipe is a hosted MCP server that takes a video file together with subtitle files and returns a video with the captions burned into the picture. It accepts MP4 video and SRT or VTT subtitle input, and the output is a captioned MP4. The service is prepaid rather than subscription-based, and it is reached as a remote endpoint rather than run locally.
- When to use it
- Use it when an assistant needs to produce a hard-coded, always-visible caption track on a video, for example for social clips, presentations, or platforms that do not render separate subtitle files. It is not needed if soft subtitles or a standalone SRT or VTT file are enough.
- Requirements
- A remote MCP connection to the provider's hosted endpoint over streamable HTTP, with OAuth sign-in required. No local runtime, package, environment variable, or header is declared. A prepaid account with the provider is implied by the prepaid, no-subscription model.
Installation
In SourceWeft
- Open CaptionPipe in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.captionpipe%2Fcaptionpipe/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"captionpipe": {
"type": "http",
"url": "https://api.captionpipe.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.