Skip to main content
Perplexity connects to the MCP server as a remote custom connector over Streamable HTTP. There is no bridge to install and no token to paste: Perplexity registers itself with the Integrate.io OAuth server and sends you to the consent screen. For OAuth detail, see Authentication. The endpoint is: https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp Replace YOUR_ACCOUNT_ID with your account subdomain or numeric id (the value in your dashboard URL).
Whether you can add custom connectors depends on your Perplexity plan and, for organization accounts, on your admin’s settings. If you don’t see the option, check with your Perplexity admin.
1

Add a remote custom connector

In Perplexity’s connector settings, add a custom connector and choose the remote option.
2

Fill in the connection details

  • Name: a recognizable label (e.g. “Integrate.io”).
  • MCP server URL: https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp
  • Authentication: OAuth.
  • Transport: Streamable HTTP.
3

Authorize and save

Perplexity opens the Integrate.io consent screen. Sign in if you aren’t already, check the return host, then click Authorize. Save the connector.
Perplexity connects from its own cloud, so the endpoint must be reachable over the public internet (the production URL is). The connection appears in Settings → Developer Settings → Connected Applications in your Integrate.io dashboard, where you can audit or revoke it.

​
Verify

Enable the connector in a thread and ask a read-only prompt, for example: “List the workspaces in my Integrate.io account.” Trouble connecting? See Troubleshooting.
Last modified on October 27, 2026