Gflow Cli vs Photoshop MCP

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

Gflow Cli logoGflow CliMultimedia Process · Local subprocess (stdio)Drive Google Flow from an agent: Veo video and Imagen image generation45FairAuth: not declaredPhotoshop MCP logoPhotoshop MCPMultimedia Process · Local subprocess (stdio)MCP server for Adobe Photoshop automation - control Photoshop from AI assistants52GoodAuth: not declared

Verdict: choose Gflow Cli 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?

Gflow Cli logoChoose Gflow Cli when

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

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.

SpecGflow Cli logoGflow CliPhotoshop MCP logoPhotoshop MCP
CategoryMultimedia ProcessMultimedia Process
Quality signal45/100 · Fair52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingBYOK (pay the provider)Free
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars323709
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Gflow Cli 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.

Gflow Cli

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gflow-cli": {
      "command": "uvx",
      "args": [
        "gflow-cli"
      ]
    }
  }
}

Photoshop MCP

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

Frequently asked questions

Gflow Cli is categorized under Multimedia Process and uses a local stdio subprocess. Photoshop MCP belongs to Multimedia Process and uses a local stdio subprocess. Pick Gflow Cli 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.

Gflow Cli is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 gflow-cli and photoshop-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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