Perplexity MCP Server

Perplexity's MCP server connects AI agents to Perplexity's online search engine and conversational reasoning models for real-time web research and citation retrieval. It allows agents to perform grounded factual queries, access up-to-date web information, verify external claims, and ingest authoritative sources with inline reference citations.

Start for free

Benefits with Ory + Perplexity MCP Server

Perplexity's MCP server gives your agents live web search with cited answers, plus deeper research and reasoning through Perplexity's models. Every question an agent asks goes to Perplexity's service, along with any internal context the agent includes. Ory Agent Security lets research agents use Perplexity while agents working with confidential data are denied it, and every tool call is attributed to the user and agent behind it.

View documentation

Use Cases

— 01 use case

Agent IAM

Research agents get Read, agents that must keep prompts in house are set to Block, and Perplexity offers nothing at Write or Admin.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Perplexity MCP server as read, write, or admin, and because the Perplexity MCP server answers questions rather than changing anything, the choice for each user, team, or agent type comes down to read for research agents or no access for agents that handle confidential prompts.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied query stops before it reaches Perplexity's service, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents send questions to Perplexity and for whom without blocking anything, so you can apply Ory's pre-built policy for the Perplexity MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Perplexity MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent shared internal context with an outside service.