Perplexity MCP Server

Advanced MCP tool for Perplexity and OpenRouter API integration. Supports both simple and complex queries with file attachments. Built with AI-first

Local serverstdioPython

What is the Perplexity MCP server?

Perplexity MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Advanced MCP tool for Perplexity and OpenRouter API integration. Supports both simple and complex queries with file attachments. Built with AI-first development approach using Cline, Cursor, and Wispr Flow.

What you get

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.

  • 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

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 2 environment variables: OPENROUTER_API_KEY, PERPLEXITY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the perplexity mcp server does with a few real requests.

How to install the Perplexity MCP server

{
  "mcpServers": {
    "perplexity-advanced": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "OPENROUTER_API_KEY": "your-value",
        "PERPLEXITY_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OPENROUTER_API_KEYCredential the server authenticates with.Yes
PERPLEXITY_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects Perplexity to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Perplexity directly.