Imageat

io.github.incendiesPublished by GitHub account incendiesv0.13.3Updated Nov 20, 2026

Generate and edit images and videos with imageat.

Overview

AI-generated overview

ImageAT server that lets an assistant generate and edit images and videos, plus publish game assets and social posts, billed to an ImageAT account.

What you can do
  • Generate images and videos from text or existing media, with async video status checks and an experimental tasks variant.
  • Apply edit features such as background removal, object eraser, relight, virtual try-on and city teleport, fetched live at startup.
  • Ask a Gemini model questions with optional image URLs and search or map grounding, and check prepaid credit balance.
  • Build browser games: search 3D model libraries, generate sprites and assets, publish and update playable links.
  • Manage Social Hub: list connected accounts and posts, create drafts, schedule or publish, cancel, and queue autopilot posts.
  • Read resources for credits, edit features, model catalogs and recent generations, and use…
When to use it
Useful when you want an assistant to produce or retouch images and video without leaving the chat, or to push generated media into social posts and game projects. Also handy for checking AI visibility of a website or asking a grounded Gemini question.
Requirements
Either the hosted remote endpoint with OAuth, or the npm package run locally via npx with Node.js. An ImageAT API key (IMAGEAT_API_KEY, starting with iat_live_) is required, and an active subscription or prepaid API balance is needed for paid generations. Self-hosting the HTTP server additionally needs MCP_OAUTH_SECRET and related settings.
Before you install
Generation and edit requests spend real money: website credits or prepaid API balance, at the same rates as the website. The API key is a live credential passed by environment variable or bearer header, so keep it out of shared configs. Social tools can publish or schedule posts to connected accounts and cancel existing ones; publishing needs an ImageAT plan. Generated media is stored and served from ImageAT CDNs.

Installation

In SourceWeft

  1. Open Imageat in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.incendies%2Fimageat/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "imageat": {
      "type": "http",
      "url": "https://mcp.imageat.com/mcp"
    }
  }
}

README

@imageat/mcp

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.

Billing. If you have an active subscription, MCP requests spend your website credits at the same rate you'd pay on imageat.com — the same generation costs the same either way. When those credits run out (or if you have no subscription), requests bill your prepaid API balance at the API tariff. Connecting a client requires one of the two.

Tools

ToolWhat it does
imageat_generate_imageText-to-image / image-to-image. Returns CDN image URL(s).
imageat_generate_videoText-to-video / image-to-video. Returns a CDN mp4 URL.
imageat_generate_video_taskExperimental MCP Tasks version with tasks/get and tasks/result.
imageat_check_video_statusChecks an asynchronous video generation until it completes.
imageat_ask_gemini_argonAsk Google's Gemini 4 Argon (optional image URLs, Google Search / Maps grounding). Returns the text answer.
imageat_check_creditsCurrent prepaid API balance (USD).
ai_visibility_checkScore how visible a website is to ChatGPT, Claude, Perplexity and AI agents (llms.txt, AI crawler rules, JSON-LD, sitemap, OpenGraph, MCP/agent files) with a fix list. Free.
imageat_game_guideStart here for a playable browser game: workflow, runtime rules and the kit API (Phaser 2D / three.js 3D). Free.
imageat_search_game_modelsSearch 2,700+ game-ready 3D library models; returns library_keys with animations. Free.
imageat_generate_game_assetOne game asset: sprite, background, texture, logo, or an AI-made 3D hero_model. Returns an asset_id.
imageat_publish_gameChecks your game code, bundles it with the engine and assets, and returns a shareable play link.
imageat_update_gamePublishes new code for one of your games as a new version (same link). Free.
imageat_social_list_accountsSocial accounts connected in imageat Social Hub (Instagram, Facebook Pages, LinkedIn, X…), whether each can post now, and autopilot schedules. Free.
imageat_social_create_postPost an image or video (a generation_id or media_url) to connected accounts: draft (default), schedule, or publish now; per-account captions. No credits; needs an imageat plan.
imageat_social_list_postsRecent Social Hub posts with each account's status and published link. Free.
imageat_social_cancel_postCancel a draft or scheduled post before it goes out. Free.
imageat_social_queue_autopilotQueue up to 30 images/videos on an autopilot; each lands in its next free weekly slot. Free.
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.

Tool results include both readable text and typed structuredContent. Tool schemas, safety annotations, and output schemas let agent clients validate calls and distinguish read-only tools.

Resources and prompts

  • imageat://account/credits — live prepaid API balance (USD).
  • imageat://edit/features — live edit-feature catalog.
  • imageat://models/images and imageat://models/videos — media model catalogs.
  • imageat://generations/recent — ten most recent account generations.
  • create-product-visual — reusable product-image workflow prompt.
  • animate-image — reusable image-to-video workflow prompt.
  • create-social-campaign, generate-and-upscale, create-creative-variants — campaign workflows.

Setup

  1. Create an API key on your ImageAT Projects page (starts with iat_live_).
  2. Add the server to your MCP client config:
json
{  "mcpServers": {    "imageat": {      "command": "npx",      "args": ["-y", "@imageat/mcp"],      "env": {        "IMAGEAT_API_KEY": "iat_live_xxxxxxxxxxxx"      }    }  }}
  1. Restart the client. The imageat_* tools will be available.

Environment variables

VarRequiredDefaultNotes
IMAGEAT_API_KEYyes—Your iat_live_ key.
IMAGEAT_BASE_URLnohttps://imageat.comThe web app that serves the /api/v1/* generation endpoints. Point at http://localhost:3000 for local dev.

Remote server (claude.ai, ChatGPT, other web clients)

The npx setup above is stdio — it works in desktop apps that launch a local process (Claude Desktop, Cursor, Claude Code). Browser clients like claude.ai and chatgpt.com instead connect to a remote MCP endpoint over Streamable HTTP.

The same tools are served over HTTP by dist/http.js. Each MCP session carries the user's own API key via the Authorization: Bearer iat_live_... header (multi-user), so this is what you point a hosted connector at.

bash
# Run the remote server locally against a local ImageAT instance:IMAGEAT_BASE_URL=http://localhost:3000 PORT=8787 npm run start:http# MCP endpoint: http://localhost:8787/mcp   ·   health: /health

Deploy it (e.g. on Dokploy as mcp.imageat.com) with the included Dockerfile, then add it as a custom connector:

  • claude.ai — Settings → Connectors → Add custom connector → URL https://mcp.imageat.com/mcp.
  • ChatGPT — Connectors / Developer mode → add server URL https://mcp.imageat.com/mcp.

Browser clients run the OAuth flow: after adding the connector they open a consent page served by this server where you paste your iat_live_ key, and the client receives a short-lived access token bound to it. Non-browser clients (mcp-remote, MCP Inspector, curl) can still send a raw iat_live_ key directly as Authorization: Bearer iat_live_....

The OAuth layer (src/oauth.ts) exposes the RFC 8414/9728 discovery docs, RFC 7591 dynamic client registration, and PKCE /authorize + /token. Expiring access and refresh tokens are encrypted with AES-256-GCM under MCP_OAUTH_SECRET; refresh tokens rotate after use and /revoke invalidates issued tokens. OAuth tokens are bound to their client ID and requested scope. Idle MCP sessions are reclaimed automatically.

VarWhereDefaultNotes
PORTremote only8787HTTP listen port.
IMAGEAT_BASE_URLbothhttps://imageat.comUpstream web app serving /api/v1/*.
MCP_OAUTH_SECRETremote only(random per boot)Long random string that encrypts issued OAuth tokens. Set this in production or tokens are invalidated on every restart.
MCP_PUBLIC_URLremote onlyderived from requestPublic origin, e.g. https://mcp.imageat.com. Only needed if proxy headers are wrong.
MCP_ALLOWED_ORIGINSremote onlyChatGPT, Claude, Cursor, VS Code, GitHub, imageatComma-separated browser Origin allowlist. Requests without an Origin (normal server-to-server clients) are unaffected.
MCP_SESSION_IDLE_MSremote only7200000Reclaim MCP sessions idle for this many milliseconds.
MCP_MAX_SESSIONSremote only500Reject new sessions with 503/Retry-After after this process reaches capacity.
INTERNAL_SERVICE_KEYremote only—Shared with the web app. Completes "Sign in with imageat" and signs the ChatGPT profile's calls so they bill website credits.
OPENAI_APPS_CHALLENGEremote only—Domain verification token from the OpenAI plugin submission, served raw at /.well-known/openai-apps-challenge.

ChatGPT app profile (/chatgpt/mcp)

The published ChatGPT app connects to https://mcp.imageat.com/chatgpt/mcp, not /mcp. It is a separate, curated profile (src/chatgpt.ts) because OpenAI's directory rules differ from other clients:

  • Fixed tool list. OpenAI reviews tools and holds new ones for approval, so the profile does not build tools from the live edit-feature catalog. Adding a tool here means it waits for review.
  • Strict content filter. Upstream calls carry X-Imageat-Surface: chatgpt, and the web app applies the restricted-account filter to every request (lib/content-restriction.ts).
  • Website credits for every account. ChatGPT users can't buy API balance in the app, so calls signed with X-Imageat-Surface-Auth (HMAC of INTERNAL_SERVICE_KEY) spend website credits (lib/api-credit-mode.ts).
  • No purchase prompts. Error text never links to pricing or top-ups.
  • Attached photos arrive through openai/fileParams as { download_url, file_id }.
  • Results render in a widget (src/widget.ts, MCP Apps ui://imageat/media-v2.html). The widget also polls imageat_check_video_status itself while a video renders.

The URL cannot be changed after the app is published without contacting OpenAI support. OAuth accepts ChatGPT's client ID metadata document (https://chatgpt.com/oauth/client.json), returns iss on authorization redirects (RFC 9207), and binds tokens to the requested resource.

Local development

bash
npm installnpm run build
# Inspect the stdio server 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

Security notes

Set a stable, long random MCP_OAUTH_SECRET in production. Browser Origins are restricted by default; add any self-hosted web client to MCP_ALLOWED_ORIGINS. Direct server-to-server clients normally omit the Origin header and continue to work with an iat_live_ bearer key.

Source: README.md at commit 300484c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.13.3LatestNov 19, 2026
  2. v0.9.1Oct 29, 2026
  3. v0.4.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts