deep_research
Conducts in-depth analysis and generates detailed reports using Perplexity's Sonar Deep Research model. Best for comprehensive research topics.
LABSCO SUMMARY
Depth becomes a choice per question instead of a setting for the whole session.
The three tools map onto three Perplexity models, so the decision a wrapper usually hides — is this worth a research pass or is it a lookup — is made per call and visible in the transcript. force_model is the escape hatch when the tool's default is wrong for a particular question. Each call carries only its query and its focus areas, so a follow-up is a fresh question rather than a continuation.
What it is
A three-tool front end to Perplexity, where the tool you call selects the model rather than the model being fixed for the session.
What you get
- Quick factual lookups through Sonar Pro
- Multi-step work — explanations, comparisons and problem-solving — through Sonar Reasoning Pro
- In-depth reports through Sonar Deep Research, narrowed by a list of focus areas passed with the question
- A force_model parameter on all three tools, so the default model behind a tool can be overridden per call
Requirements
A Perplexity account with its key in PERPLEXITY_API_KEY, and Node on the machine. MIT.
Setup effort
One command plus a key — npx -y perplexity-mcp, then supply credentials
USE CASES
01
Checking a fact in the middle of something else
The quick path goes to Sonar Pro and is meant for the straightforward question you do not want to leave the session to answer.
02
Comparing two options before committing to one
Comparisons and explanations go to Sonar Reasoning Pro, which is the model this server puts behind multi-step questions rather than lookups.
03
Getting a written brief on an area you are new to
Deep research produces a report rather than an answer, and the focus areas you pass with the question are what keep it from wandering.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
reason
Handles complex, multi-step tasks using Perplexity's Sonar Reasoning Pro model. Best for explanations, comparisons, and problem-solving.
search
Quick search for simple queries using Perplexity's Sonar Pro model. Best for straightforward questions and basic information lookup.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. Each tool runs a different Perplexity model; force_model is a parameter, not a fourth tool. All three bill your Perplexity account, and deep_research costs the most.
Requires
- npx on PATH
- PERPLEXITY_API_KEY in your environment
Where it runs
All 4 documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Build from source
TERMINAL
git clone https://github.com/DaInfernalCoder/perplexity-mcp.git
cd perplexity-mcp
npm install
npm run buildThe three local-build client entries run build/index.js from this folder — <YOUR_PATH_TO_PERPLEXITY_SERVER> is the absolute path of your perplexity-mcp clone
npx
TERMINAL
npx -y perplexity-mcpMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"perplexity": {
"command": "npx",
"args": [
"-y",
"perplexity-mcp"
],
"env": {
"PERPLEXITY_API_KEY": "<YOUR_PERPLEXITY_API_KEY>"
}
}
}
}Any MCP client — local build
ANY MCP CLIENT — LOCAL BUILD · JSON
{
"mcpServers": {
"perplexity": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PERPLEXITY_SERVER>/build/index.js"
],
"env": {
"PERPLEXITY_API_KEY": "<YOUR_PERPLEXITY_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Any MCP client — key as argument
ANY MCP CLIENT — KEY AS ARGUMENT · JSON
{
"mcpServers": {
"perplexity": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PERPLEXITY_SERVER>/build/index.js",
"--api-key",
"<YOUR_API_KEY>"
],
"disabled": false,
"autoApprove": []
}
}
}Any MCP client — key in .env file
ANY MCP CLIENT — KEY IN .ENV FILE · JSON
{
"mcpServers": {
"perplexity": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PERPLEXITY_SERVER>/build/index.js",
"--cwd",
"<YOUR_PATH_TO_PROJECT>"
],
"disabled": false,
"autoApprove": []
}
}
}<YOUR_PATH_TO_PERPLEXITY_SERVER> is the full path of your perplexity-mcp clone, and <YOUR_PATH_TO_PROJECT> is a folder that holds a .env file containing the line PERPLEXITY_API_KEY=your key. The server reads the key from that .env file, so nothing in this block carries it.
