Perplexity Browser MCP

Lets an assistant run Perplexity searches through a local browser login, returning answers, sources, and thread URLs without an API key.

What it does

This local MCP server drives a Chromium-based browser session to query Perplexity and returns the generated answer, the cited sources, and links to the resulting threads. It relies on an existing browser login rather than an API key, and can optionally store its login profile in a chosen directory.

When to use it

Useful when you want an assistant to pull Perplexity answers and citations into its workflow but you do not have or want to use a Perplexity API key. It fits desktop setups where a logged-in browser session is acceptable.

Requirements

Runs locally as a stdio process, typically started with npx from the npm package perplexity-browser-mcp. Requires a desktop environment with a Chromium-based browser and a signed-in Perplexity account. The optional environment variable PERPLEXITY_PROFILE_DIR sets an absolute directory for the local login profile.