Photoshop MCP vs Vocuno

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

Photoshop MCP logoPhotoshop MCPMultimedia Process · Local subprocess (stdio)MCP server for Adobe Photoshop automation - control Photoshop from AI assistants52GoodAuth: not declaredVocuno logoVocunoMultimedia Process · Remote HTTP/SSEOfficial Vocuno plugin for Claude that connects to Vocuno's remote MCP server for AI song generation, covers, remixes, stem separation, voice conversion, audio editing, mixing, mastering, and music analysis.74GreatAuth: oauth 2.0

Verdict: choose Photoshop MCP for multimedia process work as a local process; choose Vocuno for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

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

Vocuno logoChoose Vocuno when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Vocuno

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPhotoshop MCP logoPhotoshop MCPVocuno logoVocuno
CategoryMultimedia ProcessMultimedia Process
Quality signal52/100 · Good74/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingFreeFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars7091
Directory activity 8 views 0 installs 0 upvotes 48 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Photoshop MCP tools

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

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

Photoshop MCP

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

Vocuno

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vocuno": {
      "url": "https://vocuno.com/mcp"
    }
  }
}

Frequently asked questions

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

Photoshop MCP is listed as free. Vocuno is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 photoshop-mcp and vocuno as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Photoshop MCP has a quality signal of 52/100 (Good) with 8 views, 0 installs and 709 GitHub stars. Vocuno has 74/100 (Great) with 48 views, 0 installs and 1 GitHub stars.