A side-by-side look at the Kinocut and Proofcut MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kinocut for multimedia process work as a local process; choose Proofcut 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.
No tool names declared yet. Check the project README from the listing page.
Proofcut 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 is categorized under Multimedia Process and uses a local stdio subprocess. Proofcut belongs to Multimedia Process and uses a local stdio subprocess. Pick Kinocut for multimedia process work and Proofcut 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. Proofcut has no declared pricing — check the project's own site. 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 proofcut 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. Proofcut has 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.