Photoshop MCP vs Pipe2.ai

A side-by-side look at the Photoshop MCP and Pipe2.ai 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
P
Pipe2.aiMultimedia Process · Remote HTTP/SSE
Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.39FairAuth: no auth required

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

P
Choose Pipe2.ai when

  • You need dedicated capabilities in the Multimedia Process domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Pipe2.ai

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPhotoshop MCP logoPhotoshop MCP
P
Pipe2.ai
CategoryMultimedia ProcessMultimedia Process
Quality signal52/100 · Good39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNo auth required
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars728—
Directory activity 8 views 0 installs 0 upvotes 1 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.

Pipe2.ai 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"
      ]
    }
  }
}

Pipe2.ai

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pipe2-ai": {
      "command": "npx",
      "args": [
        "-y",
        "pipe2-ai"
      ]
    }
  }
}

Frequently asked questions

Photoshop MCP is categorized under Multimedia Process and uses a local stdio subprocess. Pipe2.ai belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Photoshop MCP for multimedia process work and Pipe2.ai 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. Pipe2.ai has no declared pricing — check the project's own site. 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 photoshop-mcp and pipe2-ai 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 728 GitHub stars. Pipe2.ai has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.