Perplexity MCP Server

A Perplexity MCP server based on https://github.com/jaacob/perplexity-mcp which includes additional tools supporting domain filtering, search recency and model routing. Exposed over MCP by the perplexity mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP server that provides Perplexity AI web search capabilities to Claude, with automatic model selection, stateful filters, and 10 purpose-built tools.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• input — string
• model — e.g. openai/gpt-4.1
• models — string[]
• preset — fast-search / pro-search / deep-research
• instructions — string
• max_steps — 1–10
• max_output_tokens — number
• tools — web_search / fetch_url

Configuration

You will need 2 environment variables: PERPLEXITY_API_KEY, PERPLEXITY_MODEL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js v20 or higher - A Perplexity API key — get one at https://www.perplexity.ai/settings/api - Claude Desktop (or any MCP-compatible client)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the perplexity mcp server does with a few real requests.

When to reach for it

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Perplexity's toolset — input, model, models and 5 more — is a fair guide to whether it matches your workflow. It is maintained by RossH121; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.