Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/photoshop-mcp/issues.md or /mcp/photoshop-mcp/issues.json, or Pod over MCP.

Reported issues for photoshop-mcp

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to photoshop-mcp.

Most discussed

UXP bridge panel never registers: manifest.json missing manifestVersion, main points at main.js

Summary

uxp-plugin/manifest.json never registers its panel entrypoint, so the UXP bridge cannot load and photoshop_neural_filter is unreachable on a clean install of v1.5.0.

Symptom

After Add Plugin → Load in UXP Developer Tool, the plugin shows State: Watching (so the manifest parses and the plugin loads), but in Photoshop:

Read the thread · 2026-08-08 · closed · external user · 1 comment

JSX bridge broken

Claude says: Confirmed: execute_script writes still don't land even after the restart — the JSX bridge in this build is just broken.

Update: Claude found this out when I told him to fix the JSX bridge: The "undefined" symptom was not a dead bridge — it's the wrapper's documented contract: your code runs inside an IIFE, so you must use an explicit return. A bare trailing expression or an assignment like app.activeDocument.activeLayer.name = "X" evaluates to undefined, so the result is "undefined

Read the thread · 2026-07-19 · closed · external user · 1 comment

JSON modification described for Claude Desktop but not Claude Code/the Claude SDK

I see in the readme it shows what JSON file where to add what to for Claude Desktop, but not for Claude Code/the Claude SDK, which I assume is something different because the directory given for Claude Desktop doesn't exist on my computer, and I've already installed two other MCP servers. But I don't remember exactly how I did it, and now I guess I have to go back and retrace my steps to add this one..

Read the thread · 2026-07-18 · closed · external user · 2 comments

"not_authenticated" when I am authenticated.

I ran npx -p @alisaitteke/photoshop-mcp photoshop-mcp-ui, it gave me a webpage for selecting my account, I selected Anthropic, then "Uses your account", and it said "not_authenticated." I already am authenticated, I'm using Claude on multiple accounts with a custom client using their SDK right now (Claude Code works too, or did the last time I tried--it should), but just to be sure, I ran claude auth login like it said and successfully logged in and clicked "Check connection & continue" aga

Read the thread · 2026-07-18 · closed · external user · 1 comment

Photoshop MCP DoJavaScript Broken on Photoshop 2026 (Windows)

Fix: Photoshop MCP DoJavaScript Broken on Photoshop 2026 (Windows)

Issue

All tools fail on Windows with Photoshop 2026 (v27.7.0). The VBS wrapper generated by WindowsExecutor executes via cscript and returns:

ERROR: The request to the Photoshop object was denied. This functionality may not be available in this version of Photoshop.
- Line 30: Illegal return statement after properties.

The photoshop_ping tool succeeds, but all other tools (get_state, get_document_info

Read the thread · 2026-06-15 · closed · external user · 2 comments

Very wonderful project! but Some problems I found during use (summarized using agent)

Photoshop MCP Tool Issues Report

Encountered while designing a 1680×1024 anime-style birthday event UI with multi-layer PSD output.

🔴 P0 — Critical

1. photoshop_place_image — False Error with Successful Execution

Parameters used:

photoshop_place_image({
  filePath: "C:/path/to/file.png",
  x: 100,
  y: 200
})

Issue: Every call returns Error placing image: No such element while the image is actually placed correctly as a Smart Object layer at the spe

Read the thread · 2026-05-18 · closed · external user · 5 comments

getContextInfo() throws "No such element" on documents without active selection - breaks get_document_info, get_layers, and many other tools

Bug

Most tools that read or modify a layer (photoshop_get_document_info, photoshop_get_layers, photoshop_create_text_layer, photoshop_set_layer_opacity, layer-ordering tools, history tools, etc.) fail with the error:

Error getting document info: No such element

…whenever the active document does not have an active selection (which is the default state right after creating or opening a document).

Root Cause

In src/api/extendscript.ts, the shared getContextInfo s

Read the thread · 2026-05-05 · closed · external user · 1 comment

Most recent

The remaining reports are on the project's issue tracker.