perplexity-web-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web using Perplexity.ai and get an AI-synthesized answer with cited sources. Uses default Perplexity settings. |
| search_advancedA | Search Perplexity.ai with specific source selection. Lets you combine multiple sources (e.g. web + academic). Use this when source control matters; prefer |
| loginA | Check if you are authenticated on Perplexity.ai. If not, opens a browser window so you can log in. |
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 3 tools
Each tool has a clear, distinct purpose: login handles authentication, search performs general queries with default settings, and search_advanced offers source control. The descriptions explicitly differentiate when to use each, eliminating ambiguity.
All tool names follow a consistent snake_case pattern with simple verbs (login, search) and a descriptive variant (search_advanced). The naming is predictable and logical.
With only 3 tools, the server is minimal but appropriately scoped for its purpose of providing Perplexity AI search capabilities. The count is on the low end but still reasonable and focused.
The tool set covers the core workflow: authentication (login) and two search modes (general and advanced). This is sufficient for most use cases; missing features like result filtering or account management are not critical gaps.