adobe-com-mcp
Related Servers
Alternatives to adobe-com-mcp
- AlicenseBqualityAmaintenanceEnables AI assistants to control Adobe Photoshop programmatically, supporting recipe workflows, state awareness, and generative AI features through natural language commands.81196,878 npm479MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants drive Adobe Photoshop on Windows through ExtendScript and COM automation, offering ~122 tools for documents, layers, text, filters, color, selections, masks, layout QA, and design systems.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to drive CorelDRAW via COM API, creating and editing documents, replacing text, manipulating shapes, running preflight checks, and batch-exporting production files from natural language instructions.-
- AlicenseCqualityAmaintenanceEnables natural-language control of Adobe Photoshop 2026 through a local, capability-gated MCP server and UXP bridge, supporting document editing, command execution, and safe automation with automatic approvals and validation.201MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to programmatically control Adobe Photoshop on Windows to create documents, manipulate layers, and manage image adjustments. It provides a bridge between the Model Context Protocol and the Photoshop Python API for automated graphic design workflows.239 PyPI302MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to control Adobe Illustrator on Windows, including creating, opening, saving, and exporting documents, drawing shapes, adding text, and running arbitrary ExtendScript.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control Adobe Photoshop through natural-language requests for tasks like background removal, portrait retouching, web and social export, carousel creation, and batch watermarking. This privacy-focused fork supports a local, free Ollama provider so prompts and images can be processed without an API key or cloud account.6,878 npmMIT
TDQS
Scored across 30 tools
Every tool targets a distinct app-specific resource and action. Photoshop and Illustrator tools are cleanly separated by prefixes, and save/export/layer/shape operations are clearly differentiated.
All tools follow the same lower_snake_case pattern with an app prefix (ps_ or ai_) followed by a verb and noun. Minor differences like ps_save_as_png vs ai_export_png are still semantically clear and predictable.
With 30 tools, the surface is too large for a single MCP server. The count is inflated by duplicating similar document and export operations across Photoshop and Illustrator, making it heavy to navigate.
Core workflows are covered: document creation, saving/exporting, basic shapes, text, layers, and filters. However, there are notable gaps such as no Illustrator open-document tool, no layer inspection, and no transform/alignment operations.