Perplexity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERPLEXITY_MODEL | No | Default model for all queries | sonar |
| PERPLEXITY_API_KEY | Yes | Your Perplexity 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perplexity_search_webB | Search the web using Perplexity AI with recency filtering |
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
There is only one tool, so there is no possibility of confusing it with another. Its purpose—web search via Perplexity with recency filtering—is unambiguous.
The single name perplexity_search_web follows a clear namespace_verb_noun pattern that would scale predictably. With only one tool no convention is actually demonstrated, so it cannot be a perfect 5.
A single tool is thin for a search server; the apparent scope (recency filtering, query modes, content retrieval) suggests more than one operation could earn a place. One tool feels underspecified rather than deliberately minimal.
Core capability (web search) is present, but there is no way to fetch full page content, retrieve citations/sources, or run structured/multi-query searches. Notable gaps an agent would hit when it needs more than a summary result.