comet-mcp is an MCP (Model Context Protocol) server used to connect Claude Code to the Perplexity Comet browser, thereby enabling agentic web browsing, deep research, and real-time task monitoring. Its core idea is "give Claude Code a browser that can think."
Purpose and Background
Existing Claude Code web tools fall mainly into two categories, each with limitations:
- Search APIs (such as Tavily, Perplexity API, WebFetch): they return static text and cannot interact, log in, or handle dynamic content. They are suitable for quick queries but are difficult for navigating complex websites or filling out forms.
- Browser automation tools (such as browser-use, Puppeteer MCP, Playwright MCP): they can interact, but they use a single-agent approach to handle everything, that is, the reasoning model writing code simultaneously decides where to click, type, and navigate. This consumes a large amount of context window and distracts attention.
Comet MCP uses a multi-agent delegation approach: Claude does not directly control the browser; instead, it delegates browsing tasks to Perplexity Comet, which is designed specifically for web research and browsing. Claude remains focused on coding tasks, while Comet handles navigation, login walls, dynamic content, and deep research. The result is that Claude's coding intelligence and Perplexity's web intelligence work together.
Main Capabilities
- Delegated web browsing: Claude sends high-level goals (such as "research X" or "log in to Y"), and Comet handles the actual clicking, scrolling, and searching, with the results returned to Claude.
- Deep research: use Perplexity Comet's web research capabilities to complete complex information gathering.
- Real-time task monitoring: supports monitoring of the task execution process.
- Cross-platform support: macOS, Windows, WSL2.
How to Use
- Configure Claude Code: add the relevant configuration in ~/.claude.json or .mcp.json (the official documentation does not provide the specific configuration content).
- Install the Comet browser: download and install Perplexity Comet.
- Use it in Claude Code: the MCP server will automatically start Comet with remotedebugging functionality when needed.
Windows and WSL Support
- Windows: works out of the box. Comet MCP automatically detects Windows and starts Comet from the default installation location.
- WSL2: mirrored networking mode is required to connect to Comet running on Windows.
- One-time setup: create or edit %USERPROFILE%.wslconfig (on the Windows side), add [wsl2] networkingMode=mirrored.
- Restart WSL: run wsl --shutdown, then reopen the WSL terminal.
- Comet MCP automatically detects WSL and uses PowerShell to communicate with Windows. If mirrored networking is unavailable, it displays an error message with setup instructions.
Custom Comet Path
If Comet is installed in a non-standard location, a custom path can be configured (the official documentation does not provide the specific configuration method).
Troubleshooting
- "Cannot connect to Comet": on macOS, ensure Comet is installed at /Applications/Comet.app; on Windows, it should be located at %LOCALAPPDATA%\Perplexity\Comet\Application; check whether port 9222 is available.
- "WSL cannot connect to Windows localhost": enable mirrored networking, or run Claude Code from Windows PowerShell instead of WSL.
- "Tools not showing in Claude": restart Claude Code after changing the configuration.
Applicable Scenarios
- Developers who need to conduct complex web research, log in, or handle dynamic content during coding.
- Users who want to separate web browsing tasks from the coding agent to avoid overloading the context window.
- Teams using Claude Code who want to enhance its web interaction capabilities.
Limitations
- Depends on the Perplexity Comet browser and Claude Code (or any MCP client).
- WSL2 requires mirrored networking mode., may be subject to system limitations.
- Specific configuration details, installation commands, and code content are not fully provided in the official documentation; refer to the repository for further understanding.
