Adding Custom Remote Connectors - Perplexity

2026-03-03 · Source: perplexity.ai via Google News · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Cloud Computing & IT Infrastructure · Depth: Intermediate, short

Summary

Perplexity now supports custom remote connectors, allowing users to integrate the platform with external data sources and tools via the Model Context Protocol (MCP). These connectors extend Perplexity's capabilities beyond its built-in options, connecting to services running locally or remotely. Organization members can add individual connectors, while admins can enable this feature for the organization and add organization-wide connectors. The process involves navigating to account or enterprise settings, selecting "Remote" for a custom connector, and providing details like the MCP Server URL (HTTPS required). Authentication options include None, API Key, or OAuth 2.0, with admins able to authenticate organization-wide OAuth connectors. Admins also control member permissions for adding custom connectors and can manage organization-wide connectors from Enterprise settings.

Key takeaway

For IT Professionals managing Perplexity deployments, you should evaluate the security implications of enabling custom remote connectors. Restrict member permissions to add connectors unless necessary, and ensure all organization-wide connectors use trusted MCP servers and appropriate authentication (API Key or OAuth 2.0). Regularly review member-added connectors for potential security risks and remove any non-compliant integrations to maintain data integrity and system security.

Key insights

Perplexity's custom remote connectors enable integration with external data sources and tools via the Model Context Protocol.

Principles

• Admins control organization-wide connector permissions.
• HTTPS is mandatory for remote MCP server URLs.

Method

To add a remote connector, navigate to settings, click "+ Custom connector," select "Remote," fill in required fields (Name, MCP Server URL), choose authentication, and acknowledge risks before adding.

In practice

• Integrate Perplexity with internal CRM systems.
• Connect to specialized local data processing tools.

Topics

• Perplexity
• Remote Connectors
• Model Context Protocol
• Connector Authentication
• Organization Permissions

Best for: AI Engineer, Software Engineer, IT Professional

Related on AIssential

• Unity AI Gateway: How to Connect Agents to External MCPs Securely — Unity AI Gateway simplifies secure agent access to external tools by centralizing authentication and governance.
• Personal Computer Is Here - Perplexity — Perplexity's Personal Computer orchestrates local and web resources to automate complex workflows on your machine.
• Article: Building a Secure MCP Server on AWS for a Million-Company B2B Platform — Treating MCP servers as first-class interfaces with narrow tool contracts enhances security and maintainability for LLM integrations.
• What is Model Context Protocol? A practical guide to MCP - Cohere — Model Context Protocol (MCP) standardizes AI application integration with enterprise systems for data access and action execution.
• Perplexity with Pipedream - Perplexity — Pipedream's Perplexity app integrates AI capabilities into automated workflows via no-code or custom code.
• Orchestrating the Platform: A Deep Dive into Model Context Protocol Servers for DevOps and Platform… — Model Context Protocol servers enable AI agents to autonomously manage complex DevOps workflows by standardizing tool interactions.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by perplexity.ai via Google News.