Perplexity Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_AI_PROXY_URL | No | URL of the sap-ai-proxy server | http://127.0.0.1:3030 |
| PERPLEXITY_DEFAULT_MODEL | No | Default Perplexity model to use | sonar-pro |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perplexity_web_searchA | Search the web using Perplexity AI with real-time information and citations. Use this for comprehensive web searches that require up-to-date information, research, and source citations. |
| perplexity_quick_searchA | Quick web search using Perplexity AI. Use this for simple queries when you need fast, real-time information with minimal configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 2 tools
The two tools have overlapping purposes—both perform web searches using Perplexity AI—but their descriptions help differentiate them: one is for 'simple queries' with 'fast, real-time information,' while the other is for 'comprehensive web searches' with 'citations.' However, the distinction is subtle and could still lead to confusion, as both essentially search the web with real-time data.
The tool names follow a consistent pattern: both use 'perplexity_' prefix and 'search' suffix, with descriptive adjectives ('quick' vs. 'web') to differentiate them. This clear and predictable naming convention makes it easy to understand their roles within the server.
With only two tools, the server feels under-scoped for a search domain, as it lacks operations like filtering results, saving searches, or managing search history. While the tools cover basic search functionality, the count is too low to provide a robust or complete search experience.
The server is severely incomplete for a search domain; it only offers two search variants without any supporting operations such as result pagination, query refinement, or citation management. This creates significant gaps that will limit an agent's ability to handle complex search tasks effectively.