This is the exact pain. Separate tabs, separate credit balances, and the script/refs living somewhere else is how half a day disappears.

MCP as the glue is the right direction. Two practical gotchas from our side when we wired video models into an MCP server: (1) checkpoint labels drift under the same marketing name week to week, so log the exact model id you actually called, and (2) fail loud when a tool only accepts N reference images instead of silently dropping the rest.

Disclosure: I run PixelDojo, and we ship an MCP path for generation too (including newer image models like P-H3-Image). Curious how you're handling auth and credit burn across Seedance / Kling / Veo in one Claude Code session.