Custom connectors: Bring your own MCP server
By Steven Van ·
Project admins can register their own remote MCP server and call it by connector ID, with Perplexity storing the credential.
Perplexity's Agent API now lets developers register their own remote MCP server as a custom connector, rather than relying only on managed integrations like Slack or GitHub. A Project administrator adds the server's name, MCP URL, and authentication (API key or none) on the Project connectors page, choosing Streamable HTTP or SSE transport, then copies the generated connector ID.
Perplexity stores the server's credential, so the requesting application only needs to pass the connector ID with type: "connector" in Agent API requests, instead of managing and sending the MCP credential itself. Custom connectors are available to all Projects.