Enable the connection
Install Node.js 22.13 or newer and download the PixelWall CLI bundle. In the desktop app, open Help, enable Allow local agent connection, and choose the export folder when prompted. PixelWall displays the launcher command; configure your MCP client to run it from the extracted CLI folder.
The launcher reads a short-lived authenticated session created by the desktop app and uses local stdio/loopback transport. One controller may use the open editor window at a time. Disable the Help-menu option, close the window, or stop the client to disconnect.
node pixelwall-mcp.mjsUse the editing and review tools
The launcher exposes inspection, project selection and import, command validation and application, operation polling and cancellation, previews, undo/redo, saving, exports, and export handoff results. Use wait:false for large batches, poll the returned operation, and include a requestKey when a caller may retry the same apply request.
capturePreview retains a session baseline for before/after review. Generated exports can be listed and read in bounded chunks, then saved through the approved folder. The browser still cannot report whether a later native download completed.
Optional anonymous MCP usage
New desktop builds offer Help → Share anonymous MCP usage, off by default. Enabling a local agent connection does not enable reporting. The separate choice shares only anonymous operation and outcome counts, including changed edits, previews, exports and verified artifact saves, with no artwork, scripts, paths or persistent identifiers.
Turn reporting off at any time from the same menu. Offline activity is not queued or backfilled. Desktop 0.5.0 and earlier cannot report MCP usage; the CLI and standalone browser bundle remain untracked.
Local safety limits
- The connection has no cloud or remote access and cannot choose an arbitrary filesystem path. Artifact saving is confined to the folder selected in PixelWall.
- Generated artifacts expire after 24 hours and are bounded to 64 files, 128 MiB total, and 64 MiB per file. Reads return at most 1 MiB per chunk and include checksum metadata.
- Cancellation is checked between commands. It does not predict the runtime of an individual command, and validation timeout is a preflight bound rather than an apply runtime guarantee.