Adobe MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 103 installs a week from npm. Last commit 24 Sep 2026.
Drive Adobe CC (AE, Photoshop, Illustrator, Premiere, Character Animator) from any MCP client
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
.readdirSync(path.join("/Applications", dir))
exec(compile(code, "<adobe-mcp>", "exec"), ns)
execFile(exe, args, { timeout: timeoutMs, killSignal: "SIGKILL", maxBuffer: 32 * 1024 * 1024 }, (err, stdout, stderr) => {
for (const e of fs.readdirSync("/Applications").filter((d) => /^Blender.*\.app$/i.test(d)).sort().reverse())
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add adobe-mcp -- npx -y @ajsmonty/adobe-mcp
{
"mcpServers": {
"adobe-mcp": {
"command": "npx",
"args": [
"-y",
"@ajsmonty/adobe-mcp"
]
}
}
}
[mcp_servers.adobe-mcp]
command = "npx"
args = ["-y", "@ajsmonty/adobe-mcp"]
{
"mcpServers": {
"adobe-mcp": {
"command": "npx",
"args": [
"-y",
"@ajsmonty/adobe-mcp"
]
}
}
}
{
"servers": {
"adobe-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ajsmonty/adobe-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
ADOBE_MCP_WORKSPACE (Directory for rendered assets, the asset registry, and learned lessons (default: ~/AdobeMCP)).
Drive Adobe Illustrator from any MCP client: artwork, type, colour, effects, data and export.
Drive Adobe Photoshop from any MCP client: layers, selections, adjustments, type and export.
Drive Adobe Premiere Pro from any MCP client: projects, sequences, timeline edits, effects, export.
Drive Adobe After Effects from any MCP client: compositions, layers, animation and rendering.
Drive Adobe InDesign from any MCP client: 135+ tools for layout, styles, books and PDF export.
Drive the Clearcote Chromium browser from any MCP client: read pages, click, fill, screenshot.
Drive Adobe Premiere Pro from an AI agent: transcript search, markers, cuts, exports, 277 tools.
Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.
Answers built from our own checks of this server.