Photoshop MCP vs Varg

A side-by-side look at the Photoshop MCP and Varg 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 declared
V
VargMultimedia Process · Local subprocess (stdio)
Generate AI video, images, speech and music (Kling, Seedance, Veo, Sora, Flux, ElevenLabs and 90+ models) through one hosted MCP server at https://mcp.varg.ai/mcp; stdio alternative: npx @vargai/mcp.53GoodAuth: oauth 2.0

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

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

V
Choose Varg when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
Explore Varg

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPhotoshop MCP logoPhotoshop MCP
V
Varg
CategoryMultimedia ProcessMultimedia Process
Quality signal52/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingFreePaid service
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars709—
Directory activity 7 views 0 installs 0 upvotes 4 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.

Varg 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"
      ]
    }
  }
}

Varg

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

Frequently asked questions

Photoshop MCP is categorized under Multimedia Process and uses a local stdio subprocess. Varg belongs to Multimedia Process and uses a local stdio subprocess. Pick Photoshop MCP for multimedia process work and Varg 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. Varg is listed as a paid service. 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 varg 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 7 views, 0 installs and 709 GitHub stars. Varg has 53/100 (Good) with 4 views, 0 installs and 0 GitHub stars.