perplexity-deep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERPLEXITY_API_KEY | Yes | Your Perplexity API key | |
| PERPLEXITY_BASE_URL | No | Base URL for the Perplexity API | https://api.perplexity.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pplx_deep_research_startA | Start a Perplexity Sonar Deep Research job. Returns a job_id immediately (does not wait for the research to finish). Use this for exhaustive multi-source investigation: literature reviews, market and competitor analysis, regulatory landscapes. After calling this, poll pplx_deep_research_check with the returned job_id. Jobs typically take 2-20 minutes. For quick factual lookups this is overkill and expensive - use a normal web search instead. |
| pplx_deep_research_checkA | Check a deep research job and retrieve the full report once it is finished. Returns immediately with the current status. If the job is still running, call again. Results stay retrievable for 7 days. |
| pplx_deep_research_listA | List recent deep research jobs with their ids, models and statuses. Use this to recover a job_id you lost, or to see what is still running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: start initiates a job, check polls/retrieves results, and list enumerates existing jobs. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern with the pplx_deep_research_ prefix (start, check, list). The naming is uniform and predictable.
Three tools are perfectly scoped for the deep research job lifecycle: initiate, monitor, and list. Each tool serves a necessary function with no redundancy.
The core workflow (start, check, list) is fully covered. A minor gap is the lack of a cancel/delete operation for long-running jobs, but this is not essential for the primary use case.