Perplexity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP bind host. Default: 127.0.0.1 | 127.0.0.1 |
| MCP_PORT | No | HTTP bind port. Default: 8000 | 8000 |
| MCP_TRANSPORT | No | Transport mode: stdio or streamable-http. Default: stdio | stdio |
| PERPLEXITY_RPM | No | Soft client-side requests/minute limit. Default: 30 | 30 |
| PERPLEXITY_API_KEY | Yes | Perplexity API key (required) | |
| PERPLEXITY_MAX_RETRIES | No | Retries on 429/5xx and transport errors. Default: 3 | 3 |
| PERPLEXITY_SEARCH_TIMEOUT | No | Search timeout in seconds. Default: 60 | 60 |
| PERPLEXITY_MAX_CONCURRENCY | No | Max concurrent API calls. Default: 2 | 2 |
| PERPLEXITY_DEEP_RESEARCH_TIMEOUT | No | Deep research timeout in seconds. Default: 180 | 180 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perplexity_searchA | General web search via Perplexity Sonar (default model: sonar-pro). |
| perplexity_deep_researchA | Comprehensive synthesis via Perplexity Sonar Deep Research. |
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 2 tools
Both tools target web search via Perplexity with nearly identical descriptions, differing only in timeout and 'deep research' label. An agent may struggle to choose between them without clear use-case differentiation.
Both tool names follow a consistent pattern: 'perplexity_search' and 'perplexity_deep_research' use the same prefix and verb_noun structure, making them clearly identifiable.
With only 2 tools, the set is minimal but arguably covers the server's purpose (search and deep research). However, the overlap reduces the value of having two separate tools.
The set only provides two search variants, lacking any additional functionalities like result filtering, history, or configuration. Important search UX features are missing, making the surface incomplete for a comprehensive search server.