Photoshop MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Photoshop-version and image-editing tool coverage as the bridge changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI-assisted Photoshop image editing with structured, undoable tool actions.

What we know

Community Photoshop MCP with a large local tool surface for layers, masks, selections, filters, text, transforms and export; recipes land as undoable Photoshop steps.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)1.7.33

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Broad Photoshop document authority. Writes: Create/update/delete layers; Masks/selections; Filters/transforms; Text; Export.
Authentication not yet verified.
Sensitive access: Photoshop documents, Images/assets

Deep write access to creative documents; use backups and review generated edits.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

519 repository stars

Stars observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Which Photoshop actions and host versions are currently supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Deep write access to creative documents; use backups and review generated edits.
Broad Photoshop document authority.
Local document/plugin data are processed locally; anonymous usage analytics are documented with opt-out.
Reviewed write actions: Create/update/delete layers; Masks/selections; Filters/transforms; Text; Export
Sensitive access: Photoshop documents, Images/assets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Requires Photoshop/plugin bridge.
Broad mutation surface can alter live documents.
Anonymous aggregated usage analytics are enabled by default but can be disabled.

Original activity observations

2026-10-05T10:07:11Z: 1.7.33

Technical identity

github.com/alisaitteke/photoshop-mcp

Exact implementation source: https://github.com/alisaitteke/photoshop-mcp ↗
Reviewed resource type: MCP Server
Repository identity: alisaitteke/photoshop-mcp
Package identity: npm:@alisaitteke/photoshop-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

GitHub repository ↗
alisaitteke/photoshop-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented setup follows; complete prerequisites and client configuration in the correct environment.
claude mcp add photoshop -- npx -y @alisaitteke/photoshop-mcp
Configure / authenticate
Publisher instructions
Requires running Photoshop on macOS/Windows and Node.js 18+. Community-maintained unofficial integration, not Adobe-endorsed. Check permissions before permitting document edits.
Advanced configuration · claude desktop json
{ "mcpServers": { "photoshop": { "args": [ "-y", "@alisaitteke/photoshop-mcp" ], "command": "npx" } } }
Check connection
Suggested check
Verify Photoshop plugin/bridge is installed and running, confirm photoshop MCP tools in the chosen client, and inspect current document state without edits. The plugin/browser app integration must be ready; an npx process alone does not prove Photoshop connectivity. Client registration check: `claude mcp get photoshop` (checks registration; inspect tools/read-only calls separately to verify authenticated service access).
Remove / uninstall / revoke
MCP100 setup guide
Remove `photoshop` from the MCP host that installed it. Close the standalone Photoshop MCP UI if running; uninstall `@alisaitteke/photoshop-mcp` only if locally installed and no other host needs it. Never remove Photoshop itself as MCP cleanup. Client disconnect (claude-code, only if registered using the name `photoshop`): `claude mcp remove photoshop`. This unregisters the client entry; it does not uninstall packages or revoke remote service credentials.
claude mcp remove photoshop

Official Documentation & Sources

What it does

Community Photoshop MCP with a large local tool surface for layers, masks, selections, filters, text, transforms and export; recipes land as undoable Photoshop steps.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing
Best fit: AI-assisted Photoshop image editing with structured, undoable tool actions.

Representative uses

Inspect document state
Create/edit layers and masks
Apply filters/transforms/text
Export creative assets

Limitations

Requires Photoshop/plugin bridge.
Broad mutation surface can alter live documents.
Anonymous aggregated usage analytics are enabled by default but can be disabled.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Broad Photoshop document authority.
Data handling: Local document/plugin data are processed locally; anonymous usage analytics are documented with opt-out.
Cost: free
Risk and cautions: Deep write access to creative documents; use backups and review generated edits.

Access scope and cautions

Write actions: Create/update/delete layers Masks/selections Filters/transforms Text Export
Sensitive access: Photoshop documents Images/assets
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect document state; Create/edit layers and masks; Apply filters/transforms/text; Export creative assets.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @alisaitteke/photoshop-mcp. Recorded transport: stdio, local_bridge. Prerequisites: Adobe Photoshop; Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local plugin/bridge; no hosted account auth documented.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete layers; Masks/selections; Filters/transforms; Text; Export. Recorded permission boundary: Broad Photoshop document authority.

What data-handling boundary should I consider?

Local document/plugin data are processed locally; anonymous usage analytics are documented with opt-out. Recorded sensitive-access context: Photoshop documents; Images/assets.

What limitations and risks should I check before use?

Deep write access to creative documents; use backups and review generated edits. Requires Photoshop/plugin bridge. Broad mutation surface can alter live documents. Anonymous aggregated usage analytics are enabled by default but can be disabled. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

Ali Sait Teke is listed as Community implementation in MCP100’s current evidence.