Connect AnimGen to Perplexity with MCP

Availability and requirements

Perplexity documents custom remote connectors as an Enterprise feature. Organization members can add one only when an administrator enables custom connectors; only administrators can share a connector with the organization. If + Custom connector is missing from your account, AnimGen cannot enable that Perplexity feature for you.

You also need a verified AnimGen account. Connecting uses OAuth and does not spend credits. A later generation still needs an explicit quote or maximum-credit approval.

Connection settings

Use the MCP server URL exactly as shown. Do not append /sse, use the tool manifest as the server URL, or substitute an API key for OAuth.

AnimGen publishes OAuth authorization-server and protected-resource metadata, supports PKCE, and exposes a dynamic client registration endpoint. Perplexity can therefore discover the OAuth endpoints and register its callback without a manually copied Client ID or Client Secret. Perplexity documents its standard callback as https://www.perplexity.ai/rest/connections/oauth_callback, or https://enterprise.perplexity.ai/rest/connections/oauth_callback on the Enterprise subdomain.

Add the connector

1. In Perplexity, open Account settings → Connectors. Organization administrators can instead use Enterprise settings → Permissions → Connectors permissions.
2. Select + Custom connector, then choose Remote.
3. Enter the values from the table above. An optional description can say: Generate animation previews and game-ready assets through the AnimGen account you authorize.
4. Confirm Perplexity's custom-connector risk acknowledgement and select Add.
5. Open the new AnimGen connector card, start authentication, sign in to AnimGen, review the requested scopes, and approve only the access you intend to grant.
6. Enable AnimGen for the Perplexity conversation before asking it to use a tool.

These UI steps and account controls follow Perplexity's current remote connector guide. Perplexity controls feature availability and may change the labels or placement.

Verify without spending credits

Start with this prompt:

Use AnimGen list_models with no arguments.
Summarize the available input modes and parameters.
Do not upload a file, request a quote, start generation, cancel a task,
or spend credits.

A structured model list confirms discovery, OAuth, and a read-only tool call. It does not prove that Perplexity can transfer local image bytes or save a downloaded asset.

Before the first generation

Confirm that the current Perplexity client can send actual image bytes or use an allowed public HTTPS image. A local path mentioned in the conversation is not an upload. Follow the standard MCP workflow for upload completion, a fresh quote, explicit approval, bounded polling, and download.

Do not approve generate_animation until Perplexity shows the exact request and credit amount. Prefer a short-lived quote_id; otherwise set a reviewed max_credits for that single operation. OAuth authorization is not spending approval.

Troubleshooting and removal

• Custom connector option is absent: ask the Perplexity organization administrator to enable member-added connectors, or use an account with the required feature.
• Connector verification returns 403: check that Cloudflare or another WAF is not challenging https://api.animgen.com/mcp or the OAuth discovery endpoints. Do not disable OAuth or expose an unauthenticated endpoint as a workaround.
• OAuth does not start: keep Authentication set to OAuth, confirm the URL has no extra path, and use API and MCP troubleshooting.
• The connector can list models but cannot use a local image: this is a client file-transfer limitation, not proof that MCP can read the path. Use a supported byte-transfer capability or an allowed public HTTPS input.

Removing the connector in Perplexity and revoking its AnimGen grant are separate actions. Remove the connector in Perplexity, then revoke the corresponding application under Account → Developer.

Perplexity search visibility is separate

Installing a connector does not make AnimGen pages rank or appear in Perplexity search answers. Search discovery uses separate agents such as PerplexityBot and Perplexity-User. AnimGen allows public crawling at the robots layer, while WAF access and actual response codes still need operational monitoring. See Perplexity's crawler documentation.