Skip to main content
Glama
fastmcp-me

Perplexity Advanced MCP

by fastmcp-me

Add to Cursor Add to VS Code Add to Claude Add to ChatGPT Add to Codex Add to Gemini

Perplexity Advanced MCP

GitHub PyPI

한국어


Overview

Perplexity Advanced MCP is an advanced integration package that leverages the OpenRouter and Perplexity APIs to provide enhanced query processing capabilities. With an intuitive command-line interface and a robust API client, this package facilitates seamless interactions with AI models for both simple and complex queries.

Related MCP server: MCP Perplexity Pro

Comparison with perplexity-mcp

While perplexity-mcp provides basic web search functionality using Perplexity AI's API, Perplexity Advanced MCP offers several additional features:

  • Multi-vendor Support: Supports both Perplexity and OpenRouter APIs, giving you flexibility in choosing your provider

  • Query Type Optimization: Distinguishes between simple and complex queries, optimizing for cost and performance

  • File Attachment Support: Allows including file contents as context in your queries, enabling more precise and contextual responses

  • Enhanced Retry Logic: Implements robust retry mechanisms for improved reliability

Overall, this is the most suitable MCP for handling codebases when integrated with editors like Cline or Cursor.

Features

  • Unified API Client: Supports both OpenRouter and Perplexity APIs with configurable models for handling simple and complex queries.

  • Command-Line Interface (CLI): Manage API key configuration and run the MCP server using Typer.

  • Advanced Query Processing: Incorporates file attachment processing, allowing you to include contextual data in your queries.

  • Robust Retry Mechanism: Utilizes Tenacity for retry logic to ensure consistent and reliable API communications.

  • Customizable Logging: Flexible logging configuration for detailed debugging and runtime monitoring.

Optimal AI Configuration

For the best experience with AI assistants (e.g., Cursor, Claude for Desktop), I recommend adding the following configuration to your project instructions or AI rules:

<perplexity-advanced-mcp>
    <description>
        Perplexity is an LLM that can search the internet, gather information, and answer users' queries.

        For example, let's suppose we want to find out the latest version of Python.
        1. You would search on Google.
        2. Then read the top two or three results directly to verify.

        Perplexity does that work for you.

        To answer a user's query, Perplexity searches, opens the top search results, finds information on those websites, and then provides the answer.

        Perplexity can be used with two types of queries: simple and complex. Choosing the right query type to fulfill the user's request is most important.
    </description>
    <simple-query>
        <description>
            It's cheap and fast. However, it's not suitable for complex queries. On average, it's more than 10 times cheaper and 3 times faster than complex queries.
            Use it for simple questions such as "What is the latest version of Python?"
        </description>
        <pricing>
            $1/M input tokens
            $1/M output tokens
        </pricing>
    </simple-query>

    <complex-query>
        <description>
            It's slower and more expensive. Compared to simple queries, it's on average more than 10 times more expensive and 3 times slower.
            Use it for more complex requests like "Analyze the attached code to examine the current status of a specific library and create a migration plan."
        </description>
        <pricing>
            $1/M input tokens
            $5/M output tokens
        </pricing>
    </complex-query>

    <instruction>
        When reviewing the user's request, if you find anything unexpected, uncertain, or questionable, **and you think you can get answer from the internet**, do not hesitate to use the "ask_perplexity" tool to consult Perplexity. However, if the internet is not required to satisfy users' request, it's meaningless to ask to perplexity.
        Since Perplexity is also an LLM, prompt engineering techniques are paramount.
        Remember the basics of prompt engineering, such as providing clear instructions, sufficient context, and examples
        Include as much context and relevant files as possible to smoothly fulfill the user's request. When adding files as attachments, make sure they are absolute paths.
    </instruction>
</perplexity-advanced-mcp>

This configuration helps AI assistants better understand when and how to use the Perplexity search functionality, optimizing for both cost and performance.

Usage

Installing via Smithery

To install Perplexity Advanced MCP for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @code-yeongyu/perplexity-advanced-mcp --client claude

Quick Start with uvx

The easiest way to run the MCP server is using uvx:

uvx perplexity-advanced-mcp -o <openrouter_api_key> # or -p <perplexity_api_key>

You can also configure the API keys using environment variables:

export OPENROUTER_API_KEY="your_key_here"
# or
export PERPLEXITY_API_KEY="your_key_here"

uvx perplexity-advanced-mcp

Note:

  • Providing both OpenRouter and Perplexity API keys simultaneously will result in an error

  • When both CLI arguments and environment variables are provided, CLI arguments take precedence

The CLI is built with Typer, ensuring a user-friendly command-line experience.

MCP Search Tool

The package includes an MCP search tool integrated via the ask_perplexity function. It supports both simple and complex queries and processes file attachments to provide additional context.

  • Simple Queries: Provides fast, efficient responses.

  • Complex Queries: Engages in detailed reasoning and supports file attachments formatted as XML.

Configuration

  • API Keys: Configure either the OPENROUTER_API_KEY or PERPLEXITY_API_KEY through command-line options or environment variables.

  • Model Selection: The configuration (in src/perplexity_advanced_mcp/config.py) maps query types to specific models:

    • OpenRouter:

      • Simple Queries: perplexity/sonar

      • Complex Queries: perplexity/sonar-reasoning

    • Perplexity:

      • Simple Queries: sonar-pro

      • Complex Queries: sonar-reasoning-pro

Development Background & Philosophy

This project emerged from my personal curiosity and experimentation. Following the recent "vibe coding" trend, over 95% of the code was written through Cline + Cursor IDE. They say "talk is cheap, show me the code" - well, with Wispr Flow's speech-to-text magic, I literally just talked and the code showed up! Most of the development was done by me saying things like "Write me the code for x y z, fix the bug here x y z." and pressing enter. Remarkably, creating this fully functional project took less than a few hours.

From project scaffolding to file structure, everything was written and reviewed through LLM. Even the GitHub Actions workflow for PyPI publishing and the release approval process were handled through Cursor. As a human developer, my role was to:

  • Starting and stopping the MCP server to help AI conduct proper testing

  • Copying and providing error logs when issues occurred

  • Finding and providing Python MCP SDK documentation and examples from the internet

  • Requesting modifications for code that didn't seem correct

In today's world where many things can be automated and replaced, I hope this MCP can help developers like you who use it to discover value beyond just writing code. May this tool assist you in becoming a new era developer who can make higher-level decisions and considerations.

Development

To contribute or modify this package:

1. Clone the Repository:

gh repo clone code-yeongyu/perplexity-advanced-mcp

2. Install Dependencies:

uv sync

3. Contribute:

Contributions are welcome! Please follow the existing code style and commit guidelines.

License

This project is licensed under the MIT License.

Available Tools

1 tool
ask_perplexityA

Perplexity is fundamentally an LLM that can search the internet, gather information, and answer users' queries.

    For example, let's suppose we want to find out the latest version of Python.
    1. You would search on Google.
    2. Then read the top two or three results directly to verify.

    Perplexity does that work for you.

    To answer a user's query, Perplexity searches, opens the top search results, finds information on those websites, and then provides the answer.

    Perplexity can be used with two types of queries: simple and complex. Choosing the right query type to fulfill the user's request is most important.

    SIMPLE Query:
    - Cheap and fast (on average, 10x cheaper and 3x faster than complex queries).
    - Suitable for straightforward questions such as "What is the latest version of Python?"
    - Pricing: $1/M input tokens, $1/M output tokens.

    COMPLEX Query:
    - Slower and more expensive (on average, 10x more expensive and 3x slower).
    - Suitable for tasks requiring multiple steps of reasoning or deep analysis, such as "Analyze the attached code to examine the current status of a specific library and create a migration plan."
    - Pricing: $1/M input tokens, $5/M output tokens.

    Instructions:
    - When reviewing the user's request, if you find anything unexpected, uncertain, or questionable, do not hesitate to use the "ask_perplexity" tool to consult Perplexity.
    - Since Perplexity is also an LLM, prompt engineering techniques are paramount.
    - Remember the basics of prompt engineering, such as providing clear instructions, sufficient context, and examples.
    - Include as much context and relevant files as possible to smoothly fulfill the user's request.
    - IMPORTANT: When adding files as attachments, you MUST use absolute paths (e.g., '/absolute/path/to/file.py'). Relative paths will not work.

    Note: All queries must be in English for optimal results.
    
ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe query to search for
query_typeYesType of query to determine model selection
attachment_pathsYesAn optional list of absolute file paths to attach as context for the search query

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It explains the search process (searches, opens top results, finds info, provides answer), pricing/speed trade-offs, and prompt engineering requirements. However, it does not explicitly state that the tool is read-only or idempotent, though implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is overly verbose, including examples and pricing details that could be streamlined. While front-loaded with purpose, it contains redundant elaboration (e.g., step-by-step hypothetical) that increases length without proportional benefit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three required parameters and no output schema, the description is highly comprehensive. It covers all parameter semantics, usage guidelines, behavioral traits, and even prompt engineering tips, making it fully complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds significant value: explains query_type enum choices with detailed use cases, and mandates absolute paths for attachment_paths. Also notes English-only for query, which is not in schema.

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 that Perplexity is an LLM that searches the internet to answer queries, with explicit examples (e.g., latest Python version) and differentiation between simple and complex queries. The verb 'ask' plus resource 'perplexity' is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: use when uncertain or questionable, and instructions for choosing query type (simple for straightforward, complex for multi-step analysis). Also mandates English queries and absolute paths for attachments, leaving no ambiguity.

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. 1 tool updatev0.1.3
    • First observedask_perplexity

TDQS

A4.4/5.0
Disambiguation5/5

With only one tool, there is no ambiguity. The purpose of 'ask_perplexity' is clearly defined as searching the internet and answering queries.

Naming Consistency5/5

The single tool name 'ask_perplexity' follows a clear verb_noun pattern, which is consistent and intuitive.

Tool Count3/5

The tool count of 1 is minimal. While the tool is comprehensive, offering both simple and complex queries, a server named 'Advanced MCP' might be expected to have additional tools for features like managing query history or retrieving sources.

Completeness4/5

The single tool covers the core functionality of searching and answering queries, including both simple and complex modes. However, there may be minor gaps such as not providing separate tools for citation or follow-up interactions.

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

Related MCP Servers

Latest Blog Posts

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/fastmcp-me/perplexity-advanced-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server