Connects to Perplexity Comet to enable agentic web browsing, deep research, and real-time task monitoring. The server allows agents to delegate complex browsing tasks, navigate dynamic websites, manage research folders, and search through Perplexity research history.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@comet-mcpresearch the top AI frameworks in 2025 and summarize the findings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
comet-mcp
Give Claude Code a browser that thinks.
An MCP server that connects Claude Code to Perplexity Comet - enabling agentic web browsing, deep research, and real-time task monitoring.

What's New in v3.0
Isolated MCP Instance - Uses a dedicated Comet browser (port 9223) - your personal tabs are never touched
Full Research Text - Fixed truncation issue, now returns complete research responses
Reliable Startup - Auto-retry logic, kills stale processes, extended timeouts
Login Detection - First-time setup prompts for Perplexity sign-in
Visual Indicator - MCP Comet shows "[MCP]" badge so you know which browser is which
Research Folders - Save and organize research into folders
Library Search - Search your existing Perplexity research history
Why?
Existing web tools for Claude Code fall into two categories, both with limitations:
1. Search APIs (Tavily, Perplexity API, WebFetch)
Return static text. No interaction, no login, no dynamic content. Great for quick lookups, but can't navigate complex sites or fill forms.
2. Browser Automation (browser-use, Puppeteer MCP, Playwright MCP)
Can interact with pages, but use a one-agent-do-all approach: the same reasoning model that's writing your code is also deciding where to click, what to type, and how to navigate. This overwhelms the context window and fragments focus.
3. Comet MCP: Multi-Agent Delegation
Comet MCP takes a different approach. Instead of Claude controlling a browser directly, it delegates to Perplexity Comet - an AI purpose-built for web research and browsing.
Claude stays focused on your coding task
Comet handles the browsing: navigation, login walls, dynamic content, deep research
Result: Claude's coding intelligence + Perplexity's web intelligence, working together
Installation (3 Steps)
Step 1: Install Comet Browser
Download: https://www.perplexity.ai/comet
Step 2: Add to Claude Code
Add to ~/.claude.json:
Step 3: macOS Setup (One-time)
Run the setup script to create an isolated MCP browser:
First Use
Restart Claude Code
Say: "Connect to Comet"
Login to Perplexity in the MCP window (first time only)
Done!
Try It
Tools
Tool | Description |
| Connect to MCP-dedicated Comet (auto-starts, isolated from personal browser) |
| Send a task and wait for response |
| Check progress on long-running tasks |
| Stop current task |
| Capture current page |
| Switch modes: search, research, labs, learn |
| List, create, or save to research folders |
| Search your existing Perplexity research |
How It Works
Port 9223: MCP uses its own port, never touches your personal Comet (9222)
Separate Profile: Data stored in
~/.comet-mcp, completely isolatedVisual Badge: MCP Comet shows "[MCP]" indicator so you know which is which
Claude sends high-level goals ("research X", "log into Y"). Comet figures out the clicks, scrolls, and searches. Results flow back to Claude.
Requirements
Node.js 18+
Claude Code (or any MCP client)
Supported platforms: macOS, Windows, WSL2
Windows & WSL Support
Native Windows
Works out of the box. Comet MCP auto-detects Windows and launches Comet from its default install location.
WSL2 (Windows Subsystem for Linux)
WSL2 requires mirrored networking to connect to Comet running on Windows:
Enable mirrored networking (one-time setup):
# Create/edit %USERPROFILE%\.wslconfig (Windows side) [wsl2] networkingMode=mirroredRestart WSL:
wsl --shutdown # Then reopen your WSL terminalThat's it! Comet MCP auto-detects WSL and uses PowerShell to communicate with Windows.
If mirrored networking isn't available, you'll see a helpful error message with setup instructions.
Custom Comet Path
If Comet is installed in a non-standard location:
Troubleshooting
"Cannot connect to Comet"
macOS: Ensure Comet is installed at
/Applications/Comet.appand you've run the one-time setup to create~/.comet-mcp/Comet-MCP.appWindows: Comet should be in
%LOCALAPPDATA%\Perplexity\Comet\Application\MCP uses port 9223 (not 9222) - check if available
"MCP Comet closes my personal Comet" (macOS)
You need to create the separate app bundle first (see "macOS: Create Isolated App Bundle" above)
Without this, Electron's single-instance lock will replace your personal browser
"Not logged in" message
Log into Perplexity in the MCP Comet browser window (the one with [MCP] badge)
Then call
comet_connectagain
"WSL cannot connect to Windows localhost"
Enable mirrored networking (see WSL section above)
Or run Claude Code from Windows PowerShell instead of WSL
"Tools not showing in Claude"
Restart Claude Code after config changes
"Research text is truncated"
Upgrade to v3.0.0 - this issue is fixed
Use
comet_pollfor long research to get full results
License
MIT