Kinocut vs TrimScript
A side-by-side look at the Kinocut and TrimScript MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TrimScriptMultimedia Process · Local subprocess (stdio)Edit video by editing the transcript. Runs locally; agent edits arrive as suggestions you approve.41FairAuth: no auth requiredVerdict: choose Kinocut for multimedia process work as a local process; choose TrimScript for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kinocut when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
TChoose TrimScript when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TrimScript | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 61/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 201 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Kinocut | View TrimScript |
Tools & capabilities
Kinocut tools
No tool names declared yet. Check the project README from the listing page.
TrimScript tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kinocut
{
"mcpServers": {
"kyanitelabs-kinocut": {
"command": "npx",
"args": [
"--yes",
"unless"
]
}
}
}
TrimScript
{
"mcpServers": {
"trimscript": {
"command": "uvx",
"args": [
"trimscript"
]
}
}
}
Frequently asked questions
Kinocut is categorized under Multimedia Process and uses a local stdio subprocess. TrimScript belongs to Multimedia Process and uses a local stdio subprocess. Pick Kinocut for multimedia process work and TrimScript for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kinocut is listed as free. Auth: no auth required. TrimScript is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kyanitelabs-kinocut and trimscript as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kinocut has a quality signal of 61/100 (Good) with 5 views, 0 installs and 201 GitHub stars. TrimScript has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.