Home › Platforms › Perplexity

Perplexity

Perplexity Agent API calls a remote MCP server over Streamable HTTP. Saved custom connectors also allow SSE.

What the docs say

The Agent API mcp tool sends a server URL and requires Streamable HTTP. A custom connector saved in the API console can use Streamable HTTP or SSE. The help-center page for the Perplexity app's local command did not load for this check, so local stdio is not included.

Auth. Managed and custom connectors store credentials on the project. The mcp tool can send authorization on the request. Connector calls run without approval unless require_approval is set.

Limits from the docs

A project administrator adds managed and custom connectors.
Custom connectors and the mcp tool do not provide the sandbox credential integration that some managed connectors do.

Setup

For one request, add a tool with type mcp, server_url, and server_label.
Or save a custom connector in the project connectors page with the MCP URL, API key or none, and Streamable HTTP or SSE.
Pass type connector and the connector id on later requests.

Sources

Perplexity Agent API MCP Checked 2026-10-17
Perplexity connectors Checked 2026-10-17

Compatibility rule

A listing is included when its directory transport token is one this platform's docs describe. The token is SSE when the transport label contains “sse”; otherwise HTTP when the label contains “http” or the listing has a hosted remote endpoint; otherwise stdio when the label contains “stdio”; otherwise undeclared. Undeclared listings are left out. This is a transport match, not a connection test. MCPwell has not run these servers inside this platform.

Directory transports counted here: remote HTTP, SSE. Only hosted remote listings are included.

Only hosted remote listings with an HTTP or SSE token are included.

Officially listed is a separate mark. It is used only when this platform's own directory or connector gallery names that server and the name matches one listing in this directory. A sentence in a setup example is not a gallery listing. The mark is not a connection test.

MCP servers (24,154)

Paid placements appear first and are labelled Sponsored or Featured; the rest are sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.

Official or reference Hosted (remote) endpoint

The first 60 cards are in the page HTML. With JavaScript, the filters page all 24,154 compatible listings.

Perplexity

What the docs say

Limits from the docs

Setup

Sources

Compatibility rule

MCP servers (24,154)

Paperclip

Nextchat

World Monitor

Netdata

Front-End Checklist

Context7 (Upstash)

Tldraw

Metabase

Reactive Resume

PostHog

Ui Tars Desktop

GitHub

Agent Skills Search Server

OpenWork MCP Gateway

Oh My Posh Validator

Skyvern

Compiler Explorer

Keploy

GitDiagram

Coder

MCP Toolbox

MCP Toolbox for Databases

OpenMetadata

Inbox Zero

Apify

Mobilerun

Nhost

openstatus

AIHOT

Sui Knowledge Base (kapa Ai)

Honcho

Firecrawl

Agent-Native Analytics

Business Contact Finder

Basebalance Cloud — X402 Rpc & Gateway

Openshorts

Airweave Search

Klavis

Treg To

Draw Io

Finance Toolkit

Ask Jev

Google Ads + Meta Ads + Ga4

Exa

Jitsu

Tradingview

Mockserver Monorepo

Cloudflare

Tolgee

NotFair-GoogleAds

Radar

Grafana

RevoGrid DataGrid MCP Pro

ShipSwift

Butterbase Oss

Supabase

Omnara

Vexa

Wacli

Medplum

First-party connectors