Set up Perplexity
Perplexity’s AI answer engine — 100M+ users. Add Agentcy as a custom remote connector and ask marketing questions alongside your research workflow. Pro, Max, and Enterprise plans.
- 01
Sign up at app.goagentcy.com and create an API key
- 02
Sign in to Perplexity (perplexity.ai) with your Pro, Max, or Enterprise account
- 03
Click your profile icon → Account settings → Connectors
- 04
Click + Custom connector in the top-right corner
- 05
In the modal, select Remote
- 06
Name: Agentcy
- 07
MCP Server URL: https://data.goagentcy.com/mcp
- 08
Authentication: API Key (or OAuth — Agentcy supports both via Dynamic Client Registration)
- 09
Transport: Streamable HTTP
- 10
Check the acknowledgement box, then click Add
- 11
Click the Agentcy connector card to authenticate — paste your agcy_... API key when prompted
- 12
Start asking marketing questions in any Perplexity conversation — Agentcy tools are now available
path: Account settings → Connectors → + Custom connector
# Remote MCP Server (OAuth)
# No config file needed — connect through your client's UI
Server URL: https://data.goagentcy.com/mcp
Authentication: OAuth
When prompted, enter your Agentcy API key (agcy_...)
Find your key at: app.goagentcy.com → Settings → API KeysCustom remote connectors require Pro ($20/mo), Max ($200/mo), or Enterprise. The Free plan does NOT support custom connectors. ENTERPRISE NOTE: organization admins control whether members can add their own custom connectors via Enterprise settings → Permissions → Connectors permissions — this is DISABLED by default. Admins can also share connectors org-wide from the same panel. Both API Key and OAuth 2.0 authentication work with Agentcy — OAuth uses Dynamic Client Registration so you don’t need to configure Client ID/Secret manually. Custom remote connectors shipped on March 13, 2026 (Perplexity’s “Bring Your Own Connector” announcement).
Stuck or want to verify these instructions yourself? These are the documentation sources we used. If something here doesn't match what you see in your client, the vendor may have updated their UI — and we'll get this page updated.