PhotoFresco

What PhotoFresco MCP server does

PhotoFresco MCP server lets an MCP client control the PhotoFresco image editor in a browser window on the user’s computer. The editor handles the actual image changes, so operations appear in its history and can be undone. The user remains in the loop by approving the connection, choosing permitted actions, and monitoring or stopping the session.

PhotoFresco supports image-editing workflows that use layers, masks, adjustment layers, selections, brushes, previews, and PSD import or export. The repository also provides a command-line interface and an agent skill, but this listing focuses on the MCP server connection.

This fits supervised workflows where an agent should make or inspect edits without receiving unrestricted access to the local filesystem. It belongs to the 🎥 Multimedia Process category and is intended for image editing rather than general file automation.

How it works

The MCP server runs locally over stdio and drives a PhotoFresco window opened through the local connector. PhotoFresco itself runs at photofresco.com in a supported browser; the editor is not included in this repository. An MCP client sends editor operations to the server, which applies them in the open editor.

The server exposes one MCP tool for each supported editor operation. Preview results are returned as images, while exports can be delivered as files or MCP resources. Because the work takes place in the editor, changes remain visible in the application’s undo history.

Folder permissions are explicit. --read folders define where the agent may open image files, and --write folders define where it may save exports and create subfolders. Without those options, the agent can still edit and preview but cannot access local image files or save exports.

Setup and configuration

PhotoFresco MCP server requires Node.js 22 or newer and an installed Chromium-based browser: Google Chrome, Microsoft Edge, or Chromium 120 or newer. The browser is not downloaded automatically. macOS is verified; Windows and Linux are implemented but not yet verified.

The server can be configured from a repository clone with a Node command, or through the provided client configuration examples. The README names Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Codex, Cline, LM Studio, Kiro, and OpenCode. Installation links are also provided for Cursor, VS Code, and LM Studio.

Use --tools to select the exposed operation groups: essentials is the default and provides at most 40 tools, while all or a comma-separated group list exposes other selections. --overwrite allows exports to replace existing files, but the agent must also request that permission. --profile selects a browser profile or an ephemeral profile, and --browser selects a different Chromium executable. The browser option can also be supplied through PHOTOFRESCO_BROWSER.

Tools and capabilities

The PhotoFresco MCP server provides:

• Editor-operation tools for image manipulation.
• Layer, mask, adjustment-layer, selection, and brush workflows.
• Image previews returned through MCP.
• Export to files or MCP resources.
• PSD import and export through the PhotoFresco editor.
• Configurable tool groups and filesystem permissions.

Limitations and notes

The PhotoFresco MCP server depends on a local browser and a running PhotoFresco editor window. The editor is hosted separately from this repository, and the README does not describe a remote or headless editing service for normal use.

The README states that the npm release is pending at the documented version, so the supplied GitHub archive, a repository clone, or the plugin route may be needed until publication. Standard setup grants no folders by default. Windows and Linux support is implemented but not verified, and the documented browser requirement is limited to Chromium-based browsers at version 120 or newer.

The repository is licensed under MIT. The server should be used when visible, user-approved editing is appropriate; it is not a substitute for unrestricted filesystem automation.