A side-by-side look at the Agenthook and Short Video Agent Kit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agenthook for multimedia process work as a local process; choose Short Video Agent Kit 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 Agenthook when
You need dedicated capabilities in the Multimedia Process domain.
No tool names declared yet. Check the project README from the listing page.
Short Video Agent Kit 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.
Agenthook is categorized under Multimedia Process and uses a local stdio subprocess. Short Video Agent Kit belongs to Multimedia Process and uses a local stdio subprocess. Pick Agenthook for multimedia process work and Short Video Agent Kit 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.
Agenthook has no declared pricing — check the project's own site. Short Video Agent Kit is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 agenthook and davidmosiah-short-video-agent-kit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agenthook has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Short Video Agent Kit has 55/100 (Good) with 8 views, 0 installs and 2 GitHub stars.