Perplexity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 tool has a single, clear purpose that cannot be confused with any other tool in the set.
The single tool name follows a consistent verb_noun pattern (perplexity_search_web), and with only one tool, there is no inconsistency to evaluate. The naming is clear and descriptive.
One tool is too few for a server with a broad purpose like web search, as it lacks related operations such as filtering results, getting details, or handling different search types. This minimal set may limit agent functionality in practical scenarios.
The server is severely incomplete for web search functionality, offering only a basic search tool without capabilities like refining queries, paginating results, or accessing cached or specific types of content. This creates significant gaps for agents trying to perform comprehensive web searches.