
Perplexity Search
Integrates Perplexity's AI API to provide chat completion capabilities with predefined prompt templates for technical documentation, code review, and other specialized use cases.
Integrates with Perplexity's web search API to enable real-time fact-checking, research, and content generation using up-to-date information.
What it does
- Generate technical documentation using AI
- Analyze security best practices
- Review and improve code
- Create API documentation in structured formats
- Use custom prompt templates
- Configure model parameters and output formats
Best for
About Perplexity Search
Perplexity Search is a community-built MCP server published by spences10 that provides AI assistants with tools and capabilities via the Model Context Protocol. Perplexity Search is an AI writing tool using real-time web search for fast fact-checking, research, and high-quality co It is categorized under ai ml, developer tools.
How to install
You can install Perplexity Search in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Perplexity Search is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
mcp-perplexity-search
⚠️ Notice
This repository is no longer maintained.
The functionality of this tool is now available in mcp-omnisearch, which combines multiple MCP tools in one unified package.
Please use mcp-omnisearch instead.
A Model Context Protocol (MCP) server for integrating Perplexity's AI API with LLMs. This server provides advanced chat completion capabilities with specialized prompt templates for various use cases.
Features
- 🤖 Advanced chat completion using Perplexity's AI models
- 📝 Predefined prompt templates for common scenarios:
- Technical documentation generation
- Security best practices analysis
- Code review and improvements
- API documentation in structured format
- 🎯 Custom template support for specialized use cases
- 📊 Multiple output formats (text, markdown, JSON)
- 🔍 Optional source URL inclusion in responses
- ⚙️ Configurable model parameters (temperature, max tokens)
- 🚀 Support for various Perplexity models including Sonar and LLaMA
Configuration
This server requires configuration through your MCP client. Here are examples for different environments:
Cline Configuration
Add this to your Cline MCP settings:
{
"mcpServers": {
"mcp-perplexity-search": {
"command": "npx",
"args": ["-y", "mcp-perplexity-search"],
"env": {
"PERPLEXITY_API_KEY": "your-perplexity-api-key"
}
}
}
}
Claude Desktop with WSL Configuration
For WSL environments, add this to your Claude Desktop configuration:
{
"mcpServers": {
"mcp-perplexity-search": {
"command": "wsl.exe",
"args": [
"bash",
"-c",
"source ~/.nvm/nvm.sh && PERPLEXITY_API_KEY=your-perplexity-api-key /home/username/.nvm/versions/node/v20.12.1/bin/npx mcp-perplexity-search"
]
}
}
}
Environment Variables
The server requires the following environment variable:
PERPLEXITY_API_KEY: Your Perplexity API key (required)
API
The server implements a single MCP tool with configurable parameters:
chat_completion
Generate chat completions using the Perplexity API with support for specialized prompt templates.
Parameters:
messages(array, required): Array of message objects with:role(string): 'system', 'user', or 'assistant'content(string): The message content
prompt_template(string, optional): Predefined template to use:technical_docs: Technical documentation with code examplessecurity_practices: Security implementation guidelinescode_review: Code analysis and improvementsapi_docs: API documentation in JSON format
custom_template(object, optional): Custom prompt template with:system(string): System message for assistant behaviourformat(string): Output format preferenceinclude_sources(boolean): Whether to include sources
format(string, optional): 'text', 'markdown', or 'json' (default: 'text')include_sources(boolean, optional): Include source URLs (default: false)model(string, optional): Perplexity model to use (default: 'sonar')temperature(number, optional): Output randomness (0-1, default: 0.7)max_tokens(number, optional): Maximum response length (default: 1024)
Development
Setup
- Clone the repository
- Install dependencies:
pnpm install
- Build the project:
pnpm build
- Run in development mode:
pnpm dev
Publishing
The project uses changesets for version management. To publish:
- Create a changeset:
pnpm changeset
- Version the package:
pnpm changeset version
- Publish to npm:
pnpm release
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License - see the LICENSE file for details.
Acknowledgments
- Built on the Model Context Protocol
- Powered by Perplexity SONAR
Alternatives
Related Skills
Browse all skillsIntegrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.
Guide for reverse engineering tools and techniques used in game security research. Use this skill when working with debuggers, disassemblers, memory analysis tools, binary analysis, or decompilers for game security research.
A semantic grep-like search tool for your local files. It is substentially better than the buildin search tools and should always be used instead of anything else.
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.
Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas.
Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.