Model Context Protocol (MCP) server for ImageAT. Gives any MCP client (Claude Desktop, Cursor, etc.) tools to generate images, generate video, and run ImageAT's image-edit features — billed against your ImageAT account credits.

Tools

Tool	What it does
`imageat_generate_image`	Text-to-image / image-to-image. Returns CDN image URL(s).
`imageat_generate_video`	Text-to-video / image-to-video. Returns a CDN mp4 URL.
`imageat_check_credits`	Current credit balance.
`imageat_edit_<feature>`	One tool per edit feature, fetched live at startup — e.g. `imageat_edit_remove-background`, `imageat_edit_object-eraser`, `imageat_edit_relight`, `imageat_edit_virtual-try-on`, `imageat_edit_city-teleport`, `imageat_edit_ai-edit-pro`. New features appear automatically.

If the feature catalog can't be reached at startup, a single generic imageat_edit_image tool (taking a feature id parameter) is registered instead, so the server still works.

Setup

Create an API key on your ImageAT Projects page (starts with iat_live_).
Add the server to your MCP client config:

{
  "mcpServers": {
    "imageat": {
      "command": "npx",
      "args": ["-y", "@imageat/mcp"],
      "env": {
        "IMAGEAT_API_KEY": "iat_live_xxxxxxxxxxxx"
      }
    }
  }
}

Restart the client. The imageat_* tools will be available.

Environment variables

Var	Required	Default	Notes
`IMAGEAT_API_KEY`	yes	—	Your `iat_live_` key.
`IMAGEAT_BASE_URL`	no	`https://imageat.com`	The web app that serves the `/api/v1/*` generation endpoints. Point at `http://localhost:3000` for local dev.

Local development

npm install
npm run build

# Inspect with the official MCP Inspector against a local ImageAT instance:
IMAGEAT_API_KEY=iat_live_... IMAGEAT_BASE_URL=http://localhost:3000 \
  npx @modelcontextprotocol/inspector node dist/index.js

Auth roadmap

Today the server authenticates with a static iat_live_ API key. Auth is isolated behind an AuthProvider interface (src/auth.ts), so a future "Sign in with ImageAT" OAuth provider can be dropped in without changing the tools, the HTTP client, or the backend /v1 routes.