Why not use OAuth?
Perplexity's connector currently expects a client secret during OAuth registration, which standard public OAuth clients don't return. An integration key avoids the problem and gives the same access.
Perplexity is great at research. With AnyToSpeech connected, it can turn what it finds into something you can listen to: an audio briefing, a narrated report or a two-host podcast.
Perplexity connects with an AnyToSpeech integration key. Its OAuth sign-in doesn't yet work with standard public OAuth clients, so the key is the reliable route.
On your AnyToSpeech Integrations page, click Create a Perplexity key. The right permissions are already selected. Copy the key: it's shown only once.
In Perplexity, open Account settings → Connectors, click + Custom connector and choose Remote. Name it AnyToSpeech and paste the server URL below.
https://anytospeech.com/api/mcp
Set Authentication to API Key and paste your integration key. Set Transport to Streamable HTTP. Tick the acknowledgement box and click Add.
Click the AnyToSpeech card to enable it. On Enterprise, an admin must first allow members to add custom connectors.
Perplexity's connector currently expects a client secret during OAuth registration, which standard public OAuth clients don't return. An integration key avoids the problem and gives the same access.
The Perplexity key comes with every AnyToSpeech tool permission selected. You can untick any you don't want before creating it, and create separate keys for different apps.
Remote connectors are added in your account settings on the web and are tied to your account.
Remove the connector in Perplexity, then revoke the key under Integration keys on your AnyToSpeech Integrations page. A revoked key stops working immediately.
Create a free AnyToSpeech account and a Perplexity integration key, then add the connector to Perplexity.