Skip to main content
Custom connectors need a Pro, Max or Enterprise plan. On Enterprise, an admin first turns on Allow members to add custom connectors under Enterprise settings → Connectors; it’s off by default (checked 2026-10-10).
1

Add a custom connector

In Perplexity: Account settings → Connectors → + Custom connector and choose Remote.
2

Describe the server

Name: AdLoop. MCP Server URL:
Authentication: OAuth. Transport: Streamable HTTP. Leave client ID and secret empty; Perplexity registers itself with AdLoop. Tick the acknowledgement and click Add.
3

Authorize

Click the AdLoop card to sign in. AdLoop’s consent page opens; sign in to your workspace and choose Allow access.
4

Use it

In the composer, turn AdLoop on in the connector picker (or type @), and make sure the search focus isn’t set to web only. Then ask: “Run the AdLoop health check.”

​
Notes

  • Perplexity only reloads a connector’s tool list when you remove and add the connector again. Do that after AdLoop gains new tools, for example a new integration.
  • Enterprise admins can share the connector with the whole organization and choose whether members sign in individually.
  • Every write goes through the preview and confirm flow: Perplexity can draft a change, but nothing is applied until you confirm it.
Your AI can read these docs too. Add https://docs.getadloop.com/mcp as an additional MCP server and your assistant can search this documentation while it works: setup answers, troubleshooting, and tool guidance on demand.