Perplexity Deep Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deep_researchB | Perform a comprehensive web search using Perplexity's Deep Research API, which provides detailed and contextually relevant results with citations. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'deep_research' has a clearly distinct and singular purpose, making it impossible for an agent to misselect among alternatives.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The name 'deep_research' follows a clear and descriptive pattern without any deviations or mixed conventions.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. While the tool is well-described for deep web research, the server's scope feels thin and underdeveloped, which could hinder agent workflows that require more granular operations.
The server is severely incomplete for a research domain, as it only offers a single broad search tool. There are obvious gaps, such as no tools for filtering results, managing queries, accessing specific sources, or performing follow-up actions, which will likely cause agent failures in complex research tasks.