Koskamo

imagic MCP MCP server

The imagic MCP server allows AI agents to control the imagic photo editor locally. It enables automated workflows such as scanning RAW photo libraries, culling images, applying user-defined editing styles, adjusting exposure and color, and exporting final results. The server runs on the user's machine, ensuring photos never leave the local environment, and supports integration with clients like Claude, Copilot, and Codex.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by imagic
MCP endpoint (Streamable HTTP)
https://mcp.imagic.ink/mcp
Vendor documentation

What you can do with it

  • Cull and rank RAW photos from a folder
  • Apply learned editing styles to images
  • Adjust exposure, color, and crop values
  • Export edited photos automatically

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http imagic-mcp https://mcp.imagic.ink/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add imagic-mcp --url https://mcp.imagic.ink/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable imagic-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "imagic-mcp": {
      "url": "https://mcp.imagic.ink/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "imagic-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.imagic.ink/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start imagic-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "imagic-mcp": {
      "type": "http",
      "url": "https://mcp.imagic.ink/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http imagic-mcp https://mcp.imagic.ink/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "imagic-mcp": {
      "url": "https://mcp.imagic.ink/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "imagic-mcp": {
      "serverUrl": "https://mcp.imagic.ink/mcp"
    }
  }
}

Do you run imagic MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing