Generate from Cursor and Claude via the Pixogen MCP

MCP is a job starter, not a hidden studio

Developers can kick a generation from Claude, ChatGPT or Cursor. The credit still comes off the same balance. Review still happens in history. /glossary/mcp is the short definition; this is the workflow.

This page is the Pixogen-specific version of the topic. Credit numbers below match the generate button in the studio as of August 2026. If a model ships a new badge, we update the routing note here within a day — that is the newsroom rule, not a landing-page rewrite.

Credit math

Same as the UI button. MCP does not discount.

Credits never expire. Failed jobs refund automatically. Do not budget as if a missed render is gone. Packs start at 200 credits for $19.99; a launch week for a persona is usually cheaper than one stock-license bundle.

Pipeline on Pixogen

Prompt in the agent → job in Pixogen → download. Do not skip the legal baseline in the agent prompt.

Internal links that belong on this job: the matching tool landing, the pipeline hub, and one glossary term. Do not leave a guide live without those three. Related reading lives in Learn and Academy, not in a footer dump.

Model routing

Pass the model slug explicitly or you inherit the tool default.

If you are choosing an engine for the first time, open /models/compare. Portraits, motion, lipsync and photoreal each have a different default. Wan 3.0 is the motion hero as of this writing; Nano Banana 2 still wins in-image text.

Mistakes that waste credits

• Putting API keys in a public repo.
• Assuming MCP bypasses consent rules.

Publish checklist

1. Lock identity before you batch.
2. Write the credit total on the brief so the client sees the number before the job.
3. Export clean — no watermark — then brand in your editor.
4. Ping the changelog if this guide rode a model drop.

See /developers, /glossary/mcp.