Perplexity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERPLEXITY_MODEL | No | The Perplexity model to use (defaults to "sonar" if not specified). Available models: sonar-deep-research, sonar-reasoning-pro, sonar-reasoning, sonar-pro, sonar, r1-1776 | sonar |
| PERPLEXITY_API_KEY | Yes | Your Perplexity AI API key |
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 |
|---|---|
| perplexity_search_webC | Search the web using Perplexity AI with recency filtering |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| perplexity_search_web | Search the web using Perplexity AI and filter results by recency |
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 single tool has a clear and distinct purpose focused on web search with Perplexity AI.
The single tool name 'perplexity_search_web' follows a consistent verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server named 'Perplexity MCP Server', which implies broader functionality. While the tool is well-defined, the server scope feels thin and limited, lacking additional operations like query refinement or result analysis that might be expected.
The server is severely incomplete for a web search domain. It only offers a basic search tool without any supporting operations such as filtering results, getting details, or managing search history, which are common in search interfaces and would be needed for agent workflows.