The production server now supports the MCP 2026-07-28 protocol, stateless Streamable HTTP, OAuth 2.1/PKCE, refresh tokens, and continued compatibility for older clients.
img-forge is also now published in the official MCP Registry, so agents can discover and connect to it more easily.
Behind the scenes, we tightened per-tier credit billing and improved the behavior of slow premium generations so agents can continue with a job instead of failing on a timeout.
I built img-forge to serve two users: the Builder, and the Builder's Agent.
Agents hit the MCP/API, generate assets inline, monitor billing, and keep moving. No friction, no context switch.
Builders get 30-day asset retention and full control over what stays and what goes.
Use cases range from storyboarding to SEO, and I'm still finding new ones every week.
I'm on a continuous journey to break it and improve it. That's not a warning. That's the pitch.