Davinci Resolve MCP vs SSTV Decoder

A side-by-side look at the Davinci Resolve MCP and SSTV Decoder MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Davinci 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
S
SSTV DecoderMultimedia Process
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.37FairAuth: not declared

Verdict: choose Davinci Resolve MCP for multimedia process work as a local process; choose SSTV Decoder for multimedia process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

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

S
Choose SSTV Decoder when

  • You need dedicated capabilities in the Multimedia Process domain.
Explore SSTV Decoder

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDavinci Resolve MCP logoDavinci Resolve MCP
S
SSTV Decoder
CategoryMultimedia ProcessMultimedia Process
Quality signal64/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,713—
Directory activity 12 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Davinci Resolve MCP tools

No tool names declared yet. Check the project README from the listing page.

SSTV Decoder 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.

Davinci Resolve MCP

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

SSTV Decoder

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

Frequently asked questions

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

Davinci Resolve MCP is listed as free. Auth: no auth required. SSTV Decoder has no declared pricing — check the project's own site. 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 samuelgursky-davinci-resolve-mcp and sstv-decoder as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Davinci Resolve MCP has a quality signal of 64/100 (Good) with 12 views, 0 installs and 3,713 GitHub stars. SSTV Decoder has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.