A
licenseB
qualityF
maintenanceA server facilitating web search functionality by utilizing Perplexity AI's API, designed to integrate with the Claude desktop client for enhanced search queries.
1
308
MIT
Perplexity MCP Server
The Perplexity MCP Server allows you to perform web searches using Perplexity AI. It provides a single tool called perplexity_search that takes a query as input and uses the Perplexity AI API to execute web searches. The server includes cross-platform support with specific setup instructions for Windows and development/production modes, and uses an .env file for API key configuration.
Allows to search the web using Perplexity AI by providing a query parameter through the 'perplexity_search' tool
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 MCP Serverfind recent advancements in quantum computing"
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 MCP Server
This is a simple MCP server that allows you to search the web using Perplexity AI.
MCP Review Certified: https://mcpreview.com/mcp-servers/spragginsdesigns/perplexity-mcp-server
Related MCP server: Tavily MCP Server
Installation
Prerequisites
Node.js 18+ (Download from nodejs.org)
Git (Download from git-scm.com)
A Perplexity AI API key
Steps for Windows
Clone the repository:
git clone [repository-url]
cd perplexity-mcp-serverInstall dependencies:
npm installCreate environment file:
Create a new file named
.envin the root directoryAdd your Perplexity AI API key:
PERPLEXITY_API_KEY=your_api_key_here
Usage on Windows
Development Mode
npm run devProduction Mode
Build the project:
npm run buildStart the server:
npm startUsing the Windows Batch File (Recommended)
To avoid environment variable issues on Windows, use the included batch file:
Build the project first:
npm run buildRun the batch file:
.\run-perplexity-server.batAlternatively, double-click the run-perplexity-server.bat file in Windows Explorer.
For detailed instructions, see the Windows Setup Guide.
Troubleshooting Windows Issues
Common Issues
Permission Errors
Run Command Prompt or PowerShell as Administrator
Check file permissions in the project directory
Environment Variables
Ensure
.envfile is in the root directoryNo spaces around the
=sign in.envfileRestart terminal after making changes to environment variables
Use the provided batch file to avoid environment variable issues
Node.js Issues
Verify Node.js installation:
node --versionEnsure npm is installed:
npm --version
Error Messages
If you see Error: ENOENT: no such file or directory, ensure:
All paths use correct Windows-style separators
You're in the correct directory
Required files exist
Project Structure
perplexity-mcp-server/
├── src/
│ └── index.ts # Main server implementation
├── dist/ # Compiled output
├── .env # Environment variables
├── package.json # Project configuration
├── run-perplexity-server.bat # Windows batch file
└── tsconfig.json # TypeScript configurationAPI Usage
The server provides a single tool perplexity_search for web searches:
{
"name": "perplexity_search",
"arguments": {
"query": "your search query here"
}
}License
MIT
Available Tools
1 toolperplexity_searchC
Search the web using Perplexity AI
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Search the web' implies a read-only operation, it doesn't address critical aspects like rate limits, authentication requirements, response format, or whether it's a real-time search versus cached results. The description is too minimal for a tool that interacts with external services.
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?
The description is extremely concise - a single sentence with zero wasted words. It's front-loaded with the core functionality and uses straightforward language. For a simple search tool, this level of brevity is appropriate.
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?
Given that there are no annotations and no output schema, the description is insufficiently complete. It doesn't explain what kind of results to expect, whether there are usage limitations, or how the search differs from standard web searches. For a tool that presumably returns search results, more context about the output would be helpful.
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?
The input schema has 100% description coverage, with the single parameter 'query' clearly documented in the schema. The description doesn't add any additional semantic context about the parameter beyond what's already in the schema, so it meets the baseline score of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Search the web') and the resource/mechanism ('using Perplexity AI'), providing a specific verb+resource combination. However, with no sibling tools mentioned, there's no opportunity to distinguish from alternatives, so it cannot achieve a perfect score of 5.
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?
The description provides no guidance on when to use this tool versus other search methods or alternatives. It simply states what the tool does without any context about appropriate use cases, prerequisites, or limitations.
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
- First observed
perplexity_search
TDQS
B3.2/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose, making it impossible for an agent to misselect between multiple options.
Naming Consistency5/5
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'perplexity_search' follows a clear verb_noun format, but consistency cannot be assessed across a set of one.
Tool Count2/5
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a web search server, this minimal scope might suffice for basic queries, but it feels thin and lacks auxiliary operations like filtering or advanced search options.
Completeness3/5
The server's purpose appears to be web search, and the single tool covers the core action of searching. However, there are notable gaps, such as no tools for refining searches, handling different search types (e.g., news, images), or managing search history, which could lead to agent workarounds or limitations.
Maintenance
ActivityInactive
ResponsivenessNo issues
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
Real-time web search, reasoning, and research through Perplexity's API
Enable AI assistants to perform web searches using Perplexity's Sonar Pro.
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
The best web search for your AI Agent
Related MCP Servers
Tavily MCP Serverofficial
AlicenseAqualityDmaintenanceThis server enables AI systems to integrate with Tavily's search and data extraction tools, providing real-time web information access and domain-specific searches.420,8992,370MIT- FlicenseBqualityNot gradedmaintenanceA server that allows AI assistants to perform web searches using Perplexity's sonar-deep-research model with citation support.111-
- AlicenseNot gradedqualityBmaintenanceA Type 3 DAuth MCP server for Perplexity AI API that provides web search, chat, embeddings, and content moderation using Perplexity's search-focused AI models.MIT
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/spragginsdesigns/perplexity-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server