update
May 2, 2026
By Teun
Community Perplexity MCP adds browser-based access for Claude and IDEs
A community-maintained project has released a Perplexity MCP runtime that works through a logged-in browser session instead of an API key. It ships as a VS Code extension and a standalone npm package for clients like Claude Desktop, Cursor, Windsurf, and others.
A community project has released an unofficial Perplexity MCP runtime that lets AI tools use a logged-in Perplexity account through a browser session, rather than a Perplexity API key. The repository says the project is experimental, not affiliated with Perplexity AI, Inc., and not intended for production use.
The monorepo ships in two main forms: perplexity-vscode, a native VS Code extension with an embedded MCP daemon, dashboard, and auto-configuration for more than 15 MCP-capable IDEs; and perplexity-user-mcp, a standalone npm package for Cursor, Claude Desktop, Claude Code, Windsurf, Cline, Amp, Codex CLI, and other MCP clients that talk over stdio. According to the project, both variants wrap the same runtime.
The main idea is that the MCP server drives a long-lived browser session against the user’s existing Perplexity account. That means the tools use the person’s logged-in Free, Pro, or Max plan instead of a separate API product.
The project says the browser automation is built with patchright and is meant to survive Cloudflare protection on first login. On first run, the server opens a headed browser so the user can sign in, then stores clearance and session data under ~/.perplexity-mcp/.
The repository also includes profile storage, encrypted cookies, and a hot-reload mechanism for state changes. If a process modifies profile state, it touches a .reinit sentinel file, which running MCP servers watch so they can reload without a restart.
The source article says the runtime mirrors Perplexity’s web app more closely than the company’s official API-key MCP server. The search-style tools accept an explicit sources array with web, scholar, and social options, and if no source is provided, the server defaults to web.
Examples in the repo show how the tools are meant to be called. A user can ask for scholar sources to search recent papers, social sources to gather practitioner discussion, or use a combined research mode that mixes sources.
The project also exposes a long-lived HTTP MCP daemon with optional tunnel support through Cloudflare Quick Tunnels or ngrok. Daemon state is stored in files such as daemon.lock, daemon.token, tunnel-settings.json, and ngrok.json.
Under the hood, the repo is organized into four npm workspaces: shared, mcp-server, webview, and extension. According to the project, build order matters because shared contracts are imported by both the extension host and the webview.
The extension side handles browser detection, auto-configuration, and the embedded daemon. It probes Chrome first, then Edge, system Chromium, Brave, and finally patchright’s bundled Chromium if needed.
The project says it writes configuration and rules files for IDEs using auto-config, updating only managed sections marked PERPLEXITY-MCP-START and PERPLEXITY-MCP-END. It lists support for VS Code, Cursor, Claude Desktop, Claude Code, Windsurf, Cline, Amp, Codex CLI, and more.
The repository is MIT licensed and maintained as a community project. It also warns that the behavior may fall under automated access or scraping under Perplexity’s terms, that Perplexity may change or block it without notice, and that the software is provided as-is.
