Skip to main content
Glama
MCP Perplexity Search

MCP Perplexity Search

by spences10

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.

Related MCP server: DocGen MCP Server

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 examples

    • security_practices: Security implementation guidelines

    • code_review: Code analysis and improvements

    • api_docs: API documentation in JSON format

  • custom_template (object, optional): Custom prompt template with:

    • system (string): System message for assistant behaviour

    • format (string): Output format preference

    • include_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

  1. Clone the repository

  2. Install dependencies:

pnpm install
  1. Build the project:

pnpm build
  1. Run in development mode:

pnpm dev

Publishing

The project uses changesets for version management. To publish:

  1. Create a changeset:

pnpm changeset
  1. Version the package:

pnpm changeset version
  1. 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

Available Tools

1 tool
chat_completionC

Generate chat completions using the Perplexity API

Inputs: messages (required), prompt_template, custom_template, format, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined as generating chat completions using the Perplexity API, leaving no room for misselection.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'chat_completion' follows a clear verb_noun pattern, and there are no other tools to compare or create inconsistencies with.

    Tool Count2/5

    A single tool is generally too few for a server's purpose, as it limits functionality and may indicate an incomplete or overly narrow scope. While it could be appropriate for a very simple service, it often feels thin and lacks the breadth needed for typical agent workflows.

    Completeness3/5

    The tool provides a core function for chat completions, but with only one tool, the surface is notably incomplete. There are obvious gaps, such as missing operations for managing conversations, handling different models, or supporting related search functionalities, which could hinder agent performance in broader tasks.

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to generate professional documentation using structured templates based on the POWER framework. Provides access to standardized templates for README, architecture, API, components, and schema documentation.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides LLMs with up-to-date, version-specific documentation and code examples from library sources directly into prompts, eliminating outdated code generation and hallucinated APIs.
      1,132,421 npm
      MIT