
Imageat
io.github.incendies由 GitHub 账号 incendies 发布v0.13.3更新于 Nov 20, 2026
Generate and edit images and videos with imageat.
概览
ImageAT 服务器,让助手生成和编辑图片与视频,并可发布游戏素材和社交媒体帖子,费用计入 ImageAT 账户。
- 可以做什么
- 根据文字或已有素材生成图片和视频,支持异步视频状态查询和实验性任务版本。
- 调用去背景、物体消除、重新打光、虚拟试穿、城市传送等编辑功能,功能列表在启动时实时获取。
- 向 Gemini 模型提问,可附带图片链接和搜索或地图 grounding,并查询预付额度余额。
- 制作浏览器游戏:搜索 3D 模型库、生成精灵图和素材、发布并更新可玩链接。
- 管理 Social Hub:列出已连接账号和帖子,创建草稿、定时或立即发布、取消,以及排队自动发布。
- 读取额度、编辑功能、模型目录和最近生成记录等资源,并使用产品图、动画和营销活动的工作流提示。
- 适用场景
- 适合希望助手在对话中直接生成或修图、制作视频的场景,也适合把生成的媒体推送到社交帖子和游戏项目。还可用于检查网站的 AI 可见性或提出带 grounding 的 Gemini 问题。
- 运行要求
- 可使用托管远程端点并通过 OAuth 连接,或在本地用 npx 运行 npm 包(需要 Node.js)。需要 ImageAT API 密钥(IMAGEAT_API_KEY,以 iat_live_ 开头),付费生成还需有效订阅或预付 API 余额。自行部署 HTTP 服务还需 MCP_OAUTH_SECRET 等配置。
安装
在 SourceWeft 中
- 打开 控制台中的 Imageat,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.incendies%2Fimageat/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"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
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/imagesandimageat://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
- Create an API key on your ImageAT Projects page (starts with
iat_live_). - Add the server to your MCP client config:
- Restart the client. The
imageat_*tools will be available.
Environment variables
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.
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.
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 ofINTERNAL_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/fileParamsas{ download_url, file_id }. - Results render in a widget (
src/widget.ts, MCP Appsui://imageat/media-v2.html). The widget also pollsimageat_check_video_statusitself 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
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.
来源:README.md,提交 300484c
工具
0版本历史
3- v0.13.3最新Nov 19, 2026
- v0.9.1Oct 29, 2026
- v0.4.0Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分