Perplexity AI 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 obtained from the dashboard |
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_searchC | Search using Perplexity AI's models with context-aware responses and citations |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching using Perplexity AI's models, making it distinct by default.
The single tool name 'perplexity_search' follows a clear and consistent verb_noun pattern (search as the verb, perplexity as a modifier). With only one tool, naming consistency is inherently perfect as there are no other tools to compare against.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a search-focused server, additional tools like filtering, citation management, or model selection might be expected to provide a more complete experience.
The server's domain appears to be search using Perplexity AI, but with only one search tool, there are significant gaps. Missing operations could include advanced search parameters, result refinement, citation handling, or integration with other Perplexity features, making the surface incomplete for typical search workflows.