Tolgee vs Davinci Resolve MCP

A side-by-side look at the Tolgee 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.

Tolgee logoTolgeeTranslation ServicesYour app's translations in Tolgee: search keys, create translations, trigger machine translation41FairAuth: not declaredDavinci Resolve MCP logoDavinci Resolve MCPMultimedia Process · Local subprocess (stdio)MCP server integration for DaVinci Resolve providing powerful tools for video editing, color grading, media management, and project control64GoodAuth: no auth required

Verdict: choose Tolgee for translation services 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?

Tolgee logoChoose Tolgee when

  • You need dedicated capabilities in the Translation Services domain.
Explore Tolgee

Davinci Resolve MCP logoChoose 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.
Explore Davinci Resolve MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTolgee logoTolgeeDavinci Resolve MCP logoDavinci Resolve MCP
CategoryTranslation ServicesMultimedia Process
Quality signal41/100 · Fair64/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4,1393,738
Directory activity 1 views 0 installs 0 upvotes 12 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Tolgee 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.

Tolgee

No confirmed install command for Tolgee yet — follow the setup steps linked from its listing page rather than a guessed package name.

Davinci Resolve MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "samuelgursky-davinci-resolve-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "davinci-resolve-mcp"
      ]
    }
  }
}

Frequently asked questions

Tolgee is categorized under Translation Services and uses an install path we have not confirmed yet. Davinci Resolve MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Tolgee for translation services work and Davinci Resolve MCP 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. Tolgee has no confirmed install command yet — follow its own setup instructions.

Tolgee has no declared pricing — check the project's own site. Davinci Resolve MCP 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 tolgee and samuelgursky-davinci-resolve-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tolgee has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 4,139 GitHub stars. Davinci Resolve MCP has 64/100 (Good) with 12 views, 0 installs and 3,738 GitHub stars.