Perplexity Comet Mcp
Let your coding agent drive Perplexity Comet for real browser sessions, tabs, and CDP-backed automation from Claude Code.
Overview
Perplexity Comet MCP is a Build-phase MCP server that bridges Claude Code (and similar agents) to Perplexity Comet for CDP-based browsing and tab management.
What is this MCP server?
- stdio MCP server (npm perplexity-comet-mcp) bridging agents to Perplexity Comet
- Autonomous browsing and tab management via Chrome DevTools Protocol
- Optional COMET_PATH for a custom Comet executable
- COMET_PORT override (default CDP port 9223)
- Explicitly positioned as a Claude Code ↔ Comet bridge
- Server version 2.5.0
- stdio transport via npm package perplexity-comet-mcp
- Default Chrome DevTools Protocol port 9223 (COMET_PORT)
Community signal: 46 GitHub stars.
What problem does it solve?
Agents cannot open, control, or coordinate real Comet browser tabs without a dedicated MCP bridge and DevTools port wiring.
Who is it for?
Indie builders already on Claude Code who rely on Perplexity Comet and want agent-driven browsing without custom CDP scripts.
Skip if: Teams that only need headless fetch/scrape APIs, lack Comet installed locally, or want hosted browser farms with no local executable.
What do I get? / Deliverables
After registration, your agent can drive Comet sessions for research flows, multi-tab tasks, and browser automation from the IDE.
- Agent-callable Comet browsing and tab management tools
- CDP-connected sessions on configurable COMET_PORT (default 9223)
- Repeatable local browser automation without custom CDP glue code
Recommended MCP Servers
Journey fit
How it compares
Local Comet CDP bridge via MCP, not a hosted web-scraping API or a passive research skill.
Common Questions / FAQ
Who is Perplexity Comet MCP for?
Solo and indie developers using Claude Code (or MCP-capable agents) who want Perplexity Comet as the live browser their agent controls.
When should I use Perplexity Comet MCP?
Use it when validating UX, filling forms, or gathering live web context that requires real tabs in Comet rather than one-shot HTTP fetches.
How do I add Perplexity Comet MCP to my agent?
Add the npm stdio server perplexity-comet-mcp to your MCP config, install Comet locally, and set COMET_PATH or COMET_PORT only if you deviate from defaults.