OpusClip vs Photoshop MCP

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

OpusClip logoOpusClipMultimedia Process · Local subprocess (stdio)Turn long videos into AI-curated short clips: caption, reframe, thumbnail, schedule, and publish.44FairAuth: not declaredPhotoshop MCP logoPhotoshop MCPMultimedia Process · Local subprocess (stdio)MCP server for Adobe Photoshop automation - control Photoshop from AI assistants52GoodAuth: not declared

Verdict: choose OpusClip for multimedia process work as a local process; choose Photoshop 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?

OpusClip logoChoose OpusClip when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
Explore OpusClip

Photoshop MCP logoChoose Photoshop MCP when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
Explore Photoshop MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOpusClip logoOpusClipPhotoshop MCP logoPhotoshop MCP
CategoryMultimedia ProcessMultimedia Process
Quality signal44/100 · Fair52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars8709
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

OpusClip tools

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

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

OpusClip

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

Photoshop MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "photoshop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@alisaitteke/photoshop-mcp",
        "ui"
      ]
    }
  }
}

Frequently asked questions

OpusClip is categorized under Multimedia Process and uses a local stdio subprocess. Photoshop MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick OpusClip for multimedia process work and Photoshop 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.

OpusClip has no declared pricing — check the project's own site. Photoshop MCP is listed as free. 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 opusclip and photoshop-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, OpusClip has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 8 GitHub stars. Photoshop MCP has 52/100 (Good) with 8 views, 0 installs and 709 GitHub stars.