Skip to main content
Glama
belugatempo-dot

Perplexity Search MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SAP_AI_PROXY_URLNoURL of the sap-ai-proxy serverhttp://127.0.0.1:3030
PERPLEXITY_DEFAULT_MODELNoDefault Perplexity model to usesonar-pro

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
perplexity_web_searchA

Search the web using Perplexity AI with real-time information and citations. Use this for comprehensive web searches that require up-to-date information, research, and source citations.

perplexity_quick_searchA

Quick web search using Perplexity AI. Use this for simple queries when you need fast, real-time information with minimal configuration.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation3/5

The two tools have overlapping purposes—both perform web searches using Perplexity AI—but their descriptions help differentiate them: one is for 'simple queries' with 'fast, real-time information,' while the other is for 'comprehensive web searches' with 'citations.' However, the distinction is subtle and could still lead to confusion, as both essentially search the web with real-time data.

Naming Consistency5/5

The tool names follow a consistent pattern: both use 'perplexity_' prefix and 'search' suffix, with descriptive adjectives ('quick' vs. 'web') to differentiate them. This clear and predictable naming convention makes it easy to understand their roles within the server.

Tool Count2/5

With only two tools, the server feels under-scoped for a search domain, as it lacks operations like filtering results, saving searches, or managing search history. While the tools cover basic search functionality, the count is too low to provide a robust or complete search experience.

Completeness2/5

The server is severely incomplete for a search domain; it only offers two search variants without any supporting operations such as result pagination, query refinement, or citation management. This creates significant gaps that will limit an agent's ability to handle complex search tasks effectively.