TAG IT Verify vs Davinci Resolve MCP
A side-by-side look at the TAG IT Verify and Davinci Resolve MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TAG IT Verify for industrial & iot work; choose Davinci Resolve MCP 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 TAG IT Verify when
- You need dedicated capabilities in the Industrial & IoT domain.
Choose Davinci Resolve MCP 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 | ||
|---|---|---|
| Category | Industrial & IoT | Multimedia Process |
| Quality signal | 35/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 3,720 |
| Directory activity | 4 views 0 installs 0 upvotes | 12 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TAG IT Verify | View Davinci Resolve MCP |
Tools & capabilities
TAG IT Verify tools
No tool names declared yet. Check the project README from the listing page.
Davinci Resolve MCP 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.
TAG IT Verify
No confirmed install command for TAG IT Verify yet — follow the setup steps linked from its listing page rather than a guessed package name.
Davinci Resolve MCP
{
"mcpServers": {
"samuelgursky-davinci-resolve-mcp": {
"command": "npx",
"args": [
"-y",
"davinci-resolve-mcp"
]
}
}
}