
ClipForge
io.github.chriphil70Published by GitHub account chriphil70v1.0.1Updated Oct 24, 2026
Trim, watermark, extract audio, and convert video to 9:16 vertical via API or MCP server.
Overview
Lets an assistant trim, watermark, extract audio from, and convert videos to 9:16 vertical format through a hosted Apify endpoint.
- What you can do
- ClipForge is a remote MCP server hosted on Apify that exposes video editing operations: trimming clips, adding watermarks, extracting audio tracks, and converting video to a 9:16 vertical aspect ratio. The registry description presents these as available via API or MCP server, so an assistant can invoke them as tools rather than editing files locally. No tool list is published in the manifest, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when an assistant needs to prepare short-form vertical video, such as reformatting landscape footage for social platforms, cutting clips, or pulling audio out of a video. It fits workflows where video processing should happen on a hosted service instead of the user's machine.
- Requirements
- A remote streamable HTTP endpoint at the provider's Apify actor URL, plus an Apify API token sent in the Authorization header formatted as 'Bearer YOUR_APIFY_TOKEN'. Network access to the endpoint is required; no local runtime or packages are declared.
Installation
In SourceWeft
- Open ClipForge in the dashboard and add it to a workspace.
- Connect Authorization token 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/io.github.chriphil70%2Fclipforge/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.
{
"mcpServers": {
"clipforge": {
"type": "http",
"url": "https://budding-retrograde--clipforge.apify.actor/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
60% 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.
- License10 pts
Declare a license in the repository or the registry entry.
