Skip to article
Documentation

Search documentation

Search stays in this browser. Queries are not sent or saved. Do not paste credentials.

Loading the public search index…

Tab or arrow keys to navigate · Enter to open · Esc to close
Browse documentation

Connect Codex and other MCP clients

Connect the live AnimGen MCP endpoint to Claude, Codex, and compatible clients using OAuth, then verify it without spending credits.

Public betaLast verified
On this page

Connection details

The official service is available in public beta:

Setting Value
Server name animgen, or a local name you choose
Server URL https://api.animgen.com/mcp
Transport Streamable HTTP
Authentication OAuth 2.1 with PKCE
Account eligibility Verified AnimGen account; active subscriptions raise limits

No API key belongs in this MCP configuration. Registered accounts use the baseline developer limits and the same credit balance as the web app. The public manifest describes tools and schemas; do not use its URL as the server.

Claude custom connector

Open Claude with AnimGen prefilled, review the server name and URL, then select Add. Start a conversation, enable AnimGen from the connectors menu, and complete the AnimGen OAuth flow when prompted.

AnimGen is offered as a custom connector, not as a claim that it appears in Claude's connector directory. Custom connector availability and organization-wide controls depend on your Claude plan and administrator settings. The setup link only prefills public connection details; it does not authorize access or spend AnimGen credits.

After connecting, use the read-only verification prompt below before trying file transfer or generation. Claude's custom connector behavior and plan requirements are documented in Anthropic's official guide.

ChatGPT developer-mode test

AnimGen is not claiming a public ChatGPT Plugin Directory listing yet. To test the production MCP server before publication, enable Developer mode under ChatGPT Settings → Security and login, open the ChatGPT Plugins page, add a new connection, and enter https://api.animgen.com/mcp as the public MCP URL. Review the discovered tools and complete OAuth before using the read-only verification prompt below.

Developer-mode availability can depend on the account and workspace policy. This connection is for testing; a public AnimGen plugin requires a separate OpenAI review and publication. Follow the current official ChatGPT plugin test guide.

Codex CLI

In your trusted terminal, add the remote server and sign in:

bash
codex mcp add animgen --url https://api.animgen.com/mcp
codex mcp login animgen

Review the AnimGen account and requested scopes in the browser authorization flow, then return to Codex. If that local server name already exists, inspect the existing configuration before replacing it. OAuth login is documented in the official Codex MCP guide; installed client versions and UI placement can differ.

Do not paste OAuth tokens into the conversation. Do not configure a generic Bearer API key as a workaround for an OAuth error.

Gemini CLI

Add AnimGen to the current user's Gemini CLI configuration:

bash
gemini mcp add --transport http --scope user animgen https://api.animgen.com/mcp

Then open Gemini CLI and complete OAuth:

text
/mcp auth animgen

Do not add an Authorization header manually and do not enable a trust bypass. Gemini CLI can discover OAuth metadata and use dynamic client registration for compatible remote HTTP servers. Use /mcp or gemini mcp list to inspect the connection, then run the read-only verification prompt below. See the official Gemini CLI MCP guide.

Other remote MCP clients

Use the client's remote-server or connector settings and enter the same URL. The client must support Streamable HTTP plus the service's OAuth discovery and authorization flow. A client that only launches local stdio servers is not equivalent.

Client availability, account plans, administrator policies, and upload/download capabilities are controlled by that client. This guide does not claim every client has been tested or that an account on another platform automatically grants AnimGen access.

If authorization fails, use connection troubleshooting; do not weaken security checks or invent redirect settings.

Verify without spending credits

Ask the connected client:

text
Use AnimGen list_models with no arguments.
Report which input modes and parameters are available.
Do not upload files, start generation, cancel tasks, or spend credits.

A structured model list confirms read-only connectivity. It does not approve any later generation or verify every downstream feature.

Next, check whether the client has an approved way to send local image bytes and save downloaded asset bytes. MCP cannot read your local file just because a path is mentioned. Follow the full workflow for upload preparation, byte transfer, completion, quote, approval, polling, and download.

Manage permission and spending

Review tool scopes and grant only the access needed. Revoke unused applications in Account → Developer. Removing a local configuration and revoking the server-side grant are separate actions.

OAuth authorization is not a credit-spending approval. Before generate_animation, approve the exact request and amount; the call needs quote_id or max_credits, with an idempotency key. See spending safeguards. Do not allow “test the connection” to become a paid generation.

Was this page helpful?

No search queries, code, or free text are collected. This switch controls documentation interactions only; general site analytics follow the privacy policy. Privacy policy

Need a hand? Contact support