AI Content Drop in Perplexity

OAuth sign-in from consumer hosts is still being verified. Public browsing and quotes work without an account; clients that accept API-key headers can use an existing key. The OAuth steps below describe the connection flow to test once sign-in is ready. Registration alone does not prove a working sign-in.

Perplexity connects to remote MCP servers through custom connectors. The steps below follow Perplexity's own help article on custom remote connectors; where that article is silent, so is this page.

Add the connector

Open the right settings page:

- for your own account: Account settings, then Connectors - for the whole organization (admins only): Enterprise settings, then Permissions, then Connectors permissions

Click + Custom connector in the top-right corner.
In the dialog, select Remote.
Fill in the required fields:

- Name: AI Content Drop - MCP Server URL: https://aicontentdrop.com/mcp (HTTPS is required)

Optional fields:

- Description: AI video and image generation on one credit balance - Authentication: OAuth - Transport: Streamable HTTP - Icon: any image up to 128 KB

Tick the acknowledgement box about the risks of custom connectors.
Click Add. The connector appears on the Connectors screen in your

Account settings.

Click the connector card to start the sign-in and enable it.

To modify or remove the connector later, click the ellipsis on its card and choose the option you want.

Sign in

Choose OAuth as the authentication method. Our server publishes OAuth discovery metadata, so Perplexity detects the endpoints and scopes itself. If the form asks for a Client ID and Client Secret, write to [email protected] and we will register one for your connector. The sign-in opens on aicontentdrop.com; approve the consent screen and the account tools start working.

Perplexity's OAuth callback URLs, should anything ask for them, are:

https://www.perplexity.ai/rest/connections/oauth_callback
https://enterprise.perplexity.ai/rest/connections/oauth_callback for

organizations on the Enterprise subdomain

API Key is also offered by Perplexity. If you prefer it, create a key at Settings → Integrations and paste it where Perplexity asks; the server accepts it as a Bearer token. None gives you the four public tools only.

Organization-wide connectors

Only admins can share a connector with the whole organization, from Enterprise settings, then Permissions. A member-added connector is private to that member. Members can add their own remote connectors only if an admin has turned on Allow members to add custom connectors, which is off by default.

For an organization-scoped connector using OAuth, an admin can sign in once on behalf of the organization, or require each member to sign in individually. Since generations bill the credits of the signed-in account, per-member sign-in is the setting that keeps each person's usage on their own account.

Try it

Ask Perplexity, with the connector selected as a source:

> Using AI Content Drop, list the video models under 20 credits.

That is list_models, which needs no account. For a generation:

> Quote a 5-second Kling 3.0 clip at 1080p, then generate one of a matcha tin > on a linen backdrop, and check on it until it is done.

The assistant calls estimate_credit_cost (which returns a quote_id valid for 15 minutes), then generate_video with that quote_id, then get_generation until the job reports completed. Credits are charged on success only.

Troubleshooting

Server validation fails during setup. Perplexity shows an error tag on the connector. Confirm the URL is exactly https://aicontentdrop.com/mcp and the transport is Streamable HTTP, then reconfigure.

Account tools answer AUTH_REQUIRED. Click the connector card and complete the sign-in, or check the key if you chose API Key.

QUOTE_REQUIRED, QUOTE_EXPIRED or QUOTE_MISMATCH. Every generation needs a fresh quote_id from estimate_credit_cost for the same model, duration and resolution. Quote again and retry.