MCP quickstart and availability

Available now in public beta

The official remote MCP is live at https://api.animgen.com/mcp. Use a compatible Streamable HTTP client with OAuth and a verified AnimGen account. Registered accounts receive baseline developer limits; active subscriptions raise them.

The MCP server runs remotely. It cannot read files from your computer just because an AI knows their paths. OAuth authorization grants access; it does not automatically upload an image or approve a credit charge.

Make the first connection

1. Follow Codex and other client setup to add the exact endpoint and complete OAuth.
2. Check the AnimGen account and requested scopes on the authorization page.
3. Call list_models with an empty argument object to verify read-only access.
4. Check whether the client can transfer local image bytes and save downloads.
5. Quote a concrete request and obtain approval before paid generation.

Do not use https://animgen.com/mcp/tools.json as a connection endpoint. It is the public documentation manifest, not the live MCP transport. Do not substitute an API key for OAuth.

Tool permissions

All eight tools have generated references and a machine-readable manifest with real argument/result schemas and safety annotations. Generation still requires account eligibility, sufficient credits, and explicit spending approval.

A safe first instruction for an AI

Use the connected AnimGen MCP to inspect current models first.
After I provide an image and intended output, explain the upload steps
and prepare a quote for the exact supported request.
Do not generate or spend credits until I approve that request and amount.
Persist the request and idempotency key. Keep credentials and signed URLs private.

Follow the standard workflow to transfer bytes, quote, generate, poll, and save files. Read spending safeguards: quote_id or max_credits is required beside request, and authorization is not spending approval.

Manage access and recover failures

Review and revoke connected applications in Account → Developer. Revocation does not cancel an accepted task. For connection, upload, or quote errors, use API and MCP troubleshooting.

Public beta means the service is usable, not that every client, media input, and target renderer has been certified. Inspect partial outputs and actual task status; a successful model query is not a full generation test.