A side-by-side look at the TrimScript and Boson Video MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TrimScript for multimedia process work as a local process; choose Boson Video 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?
T
Choose TrimScript when
You need dedicated capabilities in the Multimedia Process domain.
No tool names declared yet. Check the project README from the listing page.
Boson Video 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.
TrimScript is categorized under Multimedia Process and uses a local stdio subprocess. Boson Video belongs to Multimedia Process and uses a local stdio subprocess. Pick TrimScript for multimedia process work and Boson Video 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.
TrimScript is listed as free. Auth: no auth required. Boson Video has no declared pricing — check the project's own site. 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 trimscript and boson-video as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TrimScript has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Boson Video has 44/100 (Fair) with 0 views, 0 installs and 18 GitHub stars.