| FMRS | 60 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 |
|---|
| Best for | - Designers and creators who want to drive Photoshop conversationally without writing scripts or code
- Teams with repetitive or batch image work (watermarking, multi-platform export variants)
- Users already working inside MCP clients such as Cursor or Claude Code
- Workflows that need reversible, single-undo multi-step image operations
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Environments without Photoshop installed or running (the project depends on local Photoshop)
- Enterprises expecting official Adobe support or endorsement (this is an unofficial community project)
- Sensitive scenarios where prompts or document content must never be sent to an AI provider
- Environments that cannot install Node.js 18+ or fetch software via npm/npx
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Read and modify documents open in local Photoshop (layers, masks, color, exports, etc.)
- Run a local Node.js process that communicates with the MCP client over stdio
- Access specified local image folders for batch processing
- Use an AI provider API key, or reuse Claude Code / Gemini CLI account credentials, in standalone UI mode
- Collect anonymous aggregated usage analytics by default (can be disabled)
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - AI-planned steps modify Photoshop documents directly; although recipes are single-undo, batch or broad operations can still cause unwanted changes, so keep backups of originals.
- Generative AI features (generative fill, Firefly, etc.) require an Adobe account and may incur extra cost or be subject to service terms.
- Using a cloud AI provider means prompt text and document information read by the AI may leave your machine.
- It relies on a third-party npm package fetched and executed via npx, which carries supply-chain risk; pin versions and verify the package source.
- Anonymous usage analytics are collected by default and should be turned off if privacy matters to you.
- Batch operations modify or overwrite files in target folders, and misconfiguration can affect many files at once.
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Cursor, Claude Code, Claude Desktop, VS Code | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 0 | 26 |
|---|