MCP Perplexity Server

Created By
sibbla year ago
A MCP Perplexity API server written in Typescript with stdio and SSE transport support.
Overview

what is MCP Perplexity Server?

MCP Perplexity Server is an API server written in Typescript that allows users to interact with the Perplexity API, enabling them to ask questions to a model behind the API.

how to use MCP Perplexity Server?

To use the MCP Perplexity Server, set it up using Docker or Node.js, configure your Perplexity API key, and start the server. You can then send requests to the server endpoint to interact with the model.

key features of MCP Perplexity Server?

  • Supports both stdio and SSE transport methods.
  • Easy setup via Docker Compose.
  • Configurable options for transport and model selection.

use cases of MCP Perplexity Server?

  1. Integrating AI question-answering capabilities into applications.
  2. Building chatbots that utilize the Perplexity API for responses.
  3. Research and development of AI models using the Perplexity framework.

FAQ from MCP Perplexity Server?

  • What is required to run the MCP Perplexity Server?

You need Node.js, pnpm, and Docker to set up the server.

  • How do I configure the server?

You can configure the server by setting environment variables in the .env file, including your Perplexity API key.

  • Can I use different models with the server?

Yes, you can specify different models in the configuration options.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sibbl
Star
0
Language
TypeScript
License
MIT 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