Update: img-forge’s MCP layer just got a serious upgrade.

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.

The endpoint is still live at https://imgforge-mcp.stackbilder.com/

If you’re building with Claude Code, Codex, Cursor, or another MCP client, I’d love to hear where image generation fits in your workflow—and what the server should support next.