A
licenseA
qualityD
maintenanceAn MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.
6
4
MIT
perplexity-search-mcp
by fromdot
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@perplexity-search-mcpsearch for latest advancements in AI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
perplexity-search-mcp
MCP server for web search via Perplexity Sonar Pro through OpenRouter API.
Setup
1. Get an OpenRouter API Key
Get your API key from openrouter.ai/keys.
2. Add to MCP Client
Add to your MCP client config (e.g., AiderDesk, Claude Desktop):
{
"mcpServers": {
"perplexity-search": {
"command": "npx",
"args": ["tsx", "src/index.ts"],
"cwd": "/path/to/perplexity-search-mcp",
"env": {
"OPENROUTER_API_KEY": "sk-or-..."
}
}
}
}Or with the built version:
{
"mcpServers": {
"perplexity-search": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "/path/to/perplexity-search-mcp",
"env": {
"OPENROUTER_API_KEY": "sk-or-..."
}
}
}
}Related MCP server: perplexity-mcp-server
Tool
perplexity_search
Search the web using Perplexity Sonar Pro.
Parameter | Type | Required | Description |
| string | ✅ | The search query |
| string | ❌ | Model to use (default: |
Available models:
perplexity/sonar-pro-search(default) — deeper search, more citationsperplexity/sonar-search— faster, lighter
Development
pnpm install
pnpm build
pnpm dev # run with tsx (no build needed)License
MIT
Available Tools
1 toolperplexity_searchB
Search the web using Perplexity Sonar Pro. Returns search results with citations.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | Perplexity model to use (default: perplexity/sonar-pro-search). Options: perplexity/sonar-pro-search, perplexity/sonar-search | |
| query | Yes | The search query to look up on the web |
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only says 'returns search results with citations' but omits any details on rate limits, authentication, cost, or error handling. The read-only nature is implied but not stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero fluff. Every word adds value. The description is appropriately sized for a simple web search tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description should describe the return format. It only says 'with citations' but does not explain the structure (e.g., title, URL, snippet). This leaves the agent with incomplete information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema—it does not elaborate on the model parameter or query structure.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it searches the web and returns results with citations, naming the specific model Perplexity Sonar Pro. This leaves no ambiguity about the tool's core function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. Although there are no sibling tools, the description does not provide any context about suitable use cases or when to avoid it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v0.1.0- First observed
perplexity_search
TDQS
A3.5/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly distinct by default.
Naming Consistency5/5
Only one tool exists, so naming is trivially consistent. The name 'perplexity_search' uses a clear verb_noun pattern.
Tool Count3/5
A single tool is borderline for a server. While it may suffice for a basic search function, it feels thin and lacks supplementary tools for a richer interaction.
Completeness4/5
The server is narrowly scoped to web search via Perplexity, and the single tool covers the core operation adequately. Minor gaps like filtering or history are absent but not critical for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Serper MCP — wraps the Serper Google Search API (serper.dev)
MCP server for Google search results via SERP API
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to perform search-augmented queries and deep multi-source research using the Perplexity API.7525Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants to perform web searches and retrieve real-time information using Perplexity AI's Sonar models, with support for multiple search modes and easy integration with MCP clients.51MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that brings Perplexity's Sonar models with real-time web search capabilities to Claude Desktop and other MCP clients.419MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/fromdot/perplexity-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server