The first photo editor with a built-in MCP server

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "imagic": {
      "command": "imagic-mcp"
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "mcpServers": {
    "imagic": {
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

Cursor and most other JSON-config clients use this shape. Two known exceptions: VS Code uses servers (see its tab) and Zed uses context_servers. Add this to the client's MCP config:

{
  "mcpServers": {
    "imagic": {
      "command": "imagic-mcp",
      "args": []
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "mcpServers": {
    "imagic": {
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

One command, which writes the config for you:

code --add-mcp "{\"name\":\"imagic\",\"command\":\"imagic-mcp\"}"

Or by hand in .vscode/mcp.json. Note the top-level key is servers, not mcpServers — this is the most common reason an imagic setup that works in Cursor fails in VS Code:

{
  "servers": {
    "imagic": {
      "type": "stdio",
      "command": "imagic-mcp"
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "servers": {
    "imagic": {
      "type": "stdio",
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

Tools appear in Copilot Chat's agent mode. For a machine-wide install run MCP: Open User Configuration from the Command Palette; VS Code will prompt you to trust the server the first time it starts.

One command with the Codex CLI:

codex mcp add imagic -- imagic-mcp

Or add it to ~/.codex/config.toml:

[mcp_servers.imagic]
command = "imagic-mcp"

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

codex mcp add imagic -- "C:\Program Files\imagic\imagic.exe" --mcp

[mcp_servers.imagic]
command = "C:\\Program Files\\imagic\\imagic.exe"
args = ["--mcp"]

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

Use imagic from ChatGPT or Claude.ai

ChatGPT and Claude.ai connect from the browser, not a config file. imagic runs a small always-on relay, so there is nothing to install on the client side — just a code to type in.

1. In imagic: on the Home screen, switch on Remote control. A 6-digit code appears; leave imagic open.

2. ChatGPT (web): Settings › Security and login › Developer mode, then Plugins › Add › Create MCP App with URL https://mcp.imagic.ink/mcp and Authentication OAuth. Claude.ai: Settings › Connectors › Add custom connector, same URL.

3. A page from imagic opens and asks for the 6-digit code. Enter it and the two are paired.

Needs imagic 1.4 or newer and a Max plan or an active trial. ChatGPT needs Plus, Pro, Business or Enterprise in a browser at chatgpt.com (Developer mode is not in the desktop or mobile app yet); Claude.ai needs Pro, Max, Team or Enterprise. Full steps: ChatGPT setup · Claude.ai setup.

No AI client needed. imagic's headless mode has been scriptable since before MCP existed:

imagic --headless --scan DIR --analyse --export