PsMCP MCP Server

PsMCP MCP server exists for a simple reason — assistants are far more useful when they can act on PsMCP directly instead of describing what you should do. An Extensive MCP server and a Gradio MCP client ( with Gemini ) with several tools made using win32com to intereact with Photoshop. Designing with Photoshop has never been more fun!.

What you get

Set Gemini Key in .env bash GEMINI_API_KEY = PASTE_YOUR_KEY_HERE Set Directories for PSDs, Assets and Exports bash PSD_DIRECTORY = "D:\\Photoshop Files" EXPORT_DIRECTORY = "D:\\PsMCP-Exports" ASSETS_DIR = "D:\\PsMCP-Assets" Run the App and connect to the Server

Configuration and credentials

You will need one environment variable: GEMINI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Chandrahas455; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the psmcp mcp server does with a few real requests.