Perplexity MCP Server

Perplexity MCP Server is the official Model Context Protocol implementation for the Perplexity API Platform. It connects an MCP-capable AI client to Perplexity search and the Agent API. According to the official repository, it provides real-time web search, reasoning, and research. Perplexity hosts a Remote MCP Server at https://api.perplexity.ai/mcp; this is the easiest starting route because there is nothing to install locally and the provider operates the service. A client that supports Streamable HTTP can connect using a Perplexity API key.

Research and data analysis in a workflow

The README says that perplexity_search returns ranked web-search results with metadata and supports recency and domain filters. An agent can therefore narrow a question to current material, a time window, or known primary domains before drawing conclusions. perplexity_ask combines a general question with real-time search. For broader work, perplexity_research is intended for deep research: it uses the Agent API high preset according to the provider, can take minutes, and streams progress to clients that request it. perplexity_reason uses the medium preset for more complex analytical or problem-solving work.

That makes Research and Data Analysis appropriate categories. The server can discover current external information, gather source material for analysis, and pass results into an AI workflow. It does not replace independent data collection or expert review. Search results, summaries, and model inferences are working material. For any consequential claim, open the original source, check its date, authorship, and context, and preserve the evidence that actually supports a decision outside the chat transcript.

Remote first; local or self-hosted where needed

Perplexity describes its Remote MCP as the hosted, no-installation path with the same tools. The README names Streamable HTTP and the API endpoint. It also documents a local stdio server through npx -y @perplexity-ai/mcp-server and a self-hosted HTTP mode for cloud or shared deployments. The entry is therefore classified as both: the provider offers a remote server while also publishing local and self-hosted operating paths.

Locally, the server reads PERPLEXITY_API_KEY from the environment. The source requires the same key for a self-hosted HTTP deployment and documents the port, bind address, allowed origins, and allowed hosts. HTTP mode binds to loopback by default. If an operator deliberately exposes it, the README says to allow the public hostname and not to make CORS permissive by default. Local or self-hosted operation does not change the fact that requests go to the Perplexity API; “local” describes the MCP process, not an automatically local-only data path.

Authentication, account, and usage prerequisites

The remote endpoint uses a Perplexity API key as a Bearer token in the Authorization header. Local configurations require PERPLEXITY_API_KEY. The key is obtained through the Perplexity API Portal. Usable API access consequently depends on a Perplexity API account, its project and usage authorization, and the provider’s current terms. This entry deliberately lists no monetary amounts: check availability, limits, billing status, and enabled features in the official Perplexity API documentation and your own portal.

Never put a key in a repository, prompt, screenshot, or shared MCP file. Use secret management or the client’s secure environment-variable facilities. A header is preferable to a key in a URL, but headers can still reach debug logs or a poorly configured proxy. Rotate and revoke keys if exposure is suspected, and separate keys by person, environment, or project when the portal permits it.

Security limits and prompt injection

The server researches the open web. Pages, snippets, documents, and search results are untrusted third-party content and can include prompt-injection instructions, such as requests to ignore policy, disclose secrets, or take external actions. Treat retrieved content as data, not instructions. Do not give an agent unnecessary additional tools or secrets, independently confirm external actions, and keep the task explicit: find, extract, and cite sources rather than executing instructions found in them.

The perplexityai/modelcontextprotocol repository is MIT licensed. On 2026-09-08, the GitHub API reported exactly 2,518 stars. That is a point-in-time repository-popularity signal, not evidence of quality, privacy, research accuracy, or security.

FAQ

Is Perplexity MCP Server a remote MCP? Yes. Perplexity hosts its Remote MCP Server at https://api.perplexity.ai/mcp; the official README describes it as the easiest Streamable-HTTP starting point.

Do I still need a local installation? Not for a compatible remote client. The source also documents local stdio and self-hosted HTTP modes when a client or environment requires them.

Are research responses authoritative sources? No. Use them as a starting point and validate important claims against the linked original sources.

A Perplexity API account with an API key, an MCP-capable client, and Node.js with npx for local use; a remote client needs Streamable HTTP support.

Remote: add https://api.perplexity.ai/mcp as a Streamable HTTP server and store the Perplexity API key only as a Bearer token in the Authorization header. Local: securely set PERPLEXITY_API_KEY and use npx -y @perplexity-ai/mcp-server. For self-hosting, restrict the bind address, ALLOWED_HOSTS, and ALLOWED_ORIGINS.

npx -y @perplexity-ai/mcp-server

Remote MCP uses a Perplexity API key as a Bearer token in the Authorization header. Local and self-hosted modes require PERPLEXITY_API_KEY.

Access depends on the Perplexity API account, its project and usage authorization, and the provider’s current terms.

Search queries and tool calls go to the Perplexity API; results return to the connected MCP client and can enter its model context, logging, and retention path.

API keys can be exposed through configuration, logs, or proxies. Web content can contain prompt injection; source content must not override rules or trigger external actions.