PaintPilot
Related Servers
Alternatives to PaintPilot
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceAn MCP server that lets AI agents drive a running Adobe Photoshop from natural language — documents, layers, text, masks, selections, filters, adjustments, Smart Objects, artboards, generative tools and export — through a 9-tool facade backed by 134 operations. A dual ExtendScript/UXP transport keeps reads, saves and exports working even when Photoshop is modal, returning honest busy/timeout errors instead of silent hangs.66 npm2-
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to drive a live Adobe Photoshop session over a local UXP bridge, creating and editing documents, layers, text, selections, colours, filters and adjustments, then previewing or exporting the result. It also supports batching Photoshop action descriptors and reading Adobe's UXP reference docs.MIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables remote control of Adobe Photoshop on macOS and Windows via MCP, supporting multiple backends including AppleScript, PowerShell, and UXP plugin.13MIT
- AlicenseNot gradedqualityCmaintenanceA Windows-first local MCP server that lets Codex inspect and control Krita through a small, authenticated bridge.250 PyPI10MIT
- AlicenseAqualityDmaintenanceA professional MCP server that lets AI assistants directly control Adobe Photoshop for document creation, layer management, filters, adjustments, shapes, text, and design intelligence like palette generation and font pairing.322MIT
TDQS
Scored across 39 tools
Many tools have overlapping boundaries: photoshop_get_state, photoshop_ping, photoshop_get_document_info, and photoshop_list_documents all help establish document context; photoshop_get_capabilities and photoshop_get_painting_method_capabilities overlap; and the guard suite includes several recovery/status/lint tools whose distinctions require careful reading. The extremely long descriptions often reference other tools rather than making each tool's unique role immediately obvious.
Names are consistently snake_case, but the set mixes several prefixes and naming conventions: photoshop_* read tools, photoshop_guard_* workflow tools, and geometry tools without the photoshop_ prefix. Many guard names are process-oriented nouns or compound labels rather than a uniform verb_noun pattern.
With 39 tools, the surface is heavy for a Photoshop painting assistant and appears to expose many internal guard, recovery, validation, and diagnostics operations as first-class tools. Several tools seem specialized enough that an agent would rarely need them, inflating the set.
The server covers state inspection, previews, color sampling, brush presets, geometry, and guarded painting cycles, but obvious Photoshop lifecycle operations are missing: creating/deleting/reordering layers, direct selection editing, undo/history navigation, and save/export. Agents would likely hit dead ends for common editing workflows outside the narrow guarded painting path.