Mcp Perplexity

Created By
daniel-lxsa year ago
Overview

What is Mcp Perplexity?

Mcp Perplexity is a Python-based server that provides an interface to the Perplexity API, enabling users to query responses, maintain chat history, and manage conversations seamlessly.

How to use Mcp Perplexity?

To use Mcp Perplexity, set up your environment with the required Python version and install the necessary packages. Configure your client with the required environment variables, including your Perplexity API key, and run the server using the provided command.

Key features of Mcp Perplexity?

  • Model Configuration via Environment Variables: Customize the Perplexity model for different tools.
  • Persistent Chat History: Maintain ongoing conversations with full context.
  • Streaming Responses with Progress Reporting: Handle slow responses effectively.
  • Web UI: An interactive interface for managing chats and viewing history.

Use cases of Mcp Perplexity?

  1. Debugging and coding assistance through the ask_perplexity tool.
  2. Ongoing conversations for research and technical discussions using chat_perplexity.
  3. Managing and retrieving chat histories for analysis or review.

FAQ from Mcp Perplexity?

  • What programming language is used?

Mcp Perplexity is built using Python.

  • Is there a web interface?

Yes, a web UI is available for easier interaction when enabled.

  • How do I configure the server?

Configuration is done through environment variables, including API keys and model settings.

Server Config

{
  "mcpServers": {
    "mcp-perplexity": {
      "command": "uvx",
      "args": [
        "mcp-perplexity"
      ],
      "env": {
        "PERPLEXITY_API_KEY": "your-api-key",
        "PERPLEXITY_MODEL": "sonar-pro",
        "DB_PATH": "chats.db"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
daniel-lxs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago