Log inSubmit server

Locize vs Davinci Resolve MCP

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

L
LocizeTranslation Services · Remote HTTP/SSELocize MCP server: read/write translations, publish versions, manage branches from AI assistants.42FairAuth: 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 Locize for translation services work over a hosted endpoint; 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?

L
Choose Locize when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a remote HTTP/SSE transport.
Explore Locize

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.

Spec
L
Locize		Davinci Resolve MCP logoDavinci Resolve MCP
CategoryTranslation ServicesMultimedia Process
Quality signal42/100 · Fair64/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—3,701
Directory activity 2 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Locize View Davinci Resolve MCP

Tools & capabilities

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

Locize

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "locize": {
      "url": "https://www.locize.com/docs/integration/mcp"
    }
  }
}

Davinci Resolve MCP

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

Frequently asked questions

Locize is categorized under Translation Services and uses a remote HTTP/SSE transport. Davinci Resolve MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Locize 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.

Locize 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 locize and samuelgursky-davinci-resolve-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Locize has a quality signal of 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Davinci Resolve MCP has 64/100 (Good) with 11 views, 0 installs and 3,701 GitHub stars.

Popular comparisons with Locize

Popular comparisons with Davinci Resolve MCP