perplexity-polza-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| POLZA_BASE_URL | No | Base URL for chat completions | https://polza.ai/api/v1 |
| PERPLEXITY_MODEL | No | Model for perplexity_ask tool | perplexity/sonar |
| POLZA_AI_API_KEY | Yes | API key from polza.ai | |
| PERPLEXITY_RESEARCH_MODEL | No | Model for perplexity_research tool | perplexity/sonar-deep-research |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perplexity_askD | – |
| perplexity_researchD | – |
| list_perplexity_modelsD | – |
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
Tool names suggest distinct purposes: listing models, asking a question, and doing research. However, the lack of descriptions creates some ambiguity about each tool's exact scope.
Naming is inconsistent: one tool uses a verb_noun pattern (list_perplexity_models), while the other two use a brand prefix followed by a verb (perplexity_ask, perplexity_research). The convention is not uniform.
Three tools is on the lower side but could be sufficient for a focused server (e.g., listing models, asking questions, researching). However, the lack of descriptions makes the scope feel underdeveloped.
The tool set covers basic interactions with Perplexity (list models, ask, research), but without descriptions it's unclear if common operations like context management or follow-up questions are supported. The surface appears minimal but possibly complete for simple use cases.