# hanzili/comet-mcp [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/hanzili/comet-mcp  
**GitHub Stars:** 179  
**npm Downloads (last month):** 334  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hanzili-comet-mcp

## Description
Connect to Perplexity Comet browser for agentic web browsing, deep research, and real-time task monitoring.

## Tools
Capabilities this server exposes over MCP:

- **comet_connect** — Connect to Comet (auto-starts if needed)
- **comet_ask** — Send a task and wait for response
- **comet_poll** — Check progress on long-running tasks
- **comet_stop** — Stop current task
- **comet_screenshot** — Capture current page
- **comet_mode** — Switch modes: search, research, labs, learn

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "comet-mcp": {
    "command": "npx",
    "args": ["-y","comet-mcp"]
  }
}
```

## Documentation

## What hanzili/comet-mcp MCP server does

The hanzili/comet-mcp MCP server bridges an MCP client to the Perplexity Comet browser. Rather than exposing low-level click and typing controls, it lets the client delegate a browsing goal to Comet, which handles navigation, searches, dynamic pages, login walls, and research workflows. Results are returned to the MCP client after Comet completes the requested work.

The server is suited to tasks such as researching a topic, checking information on a site that requires interaction, or asking Comet to navigate an authenticated web session. It is not presented as a general-purpose search API or a direct browser-control toolkit.

## How it works

The local process communicates with Comet through the Chrome DevTools Protocol, using Comet's remote debugging interface. The general flow is an MCP client sending a goal to the server, the server forwarding it to Comet, and Comet using Perplexity's browser-oriented agent to perform the web task. The client can then receive the result or inspect progress while a task continues.

Connection handling is built into the server. The `comet_connect` tool connects to an existing Comet process or starts one when needed. The documented setup uses Comet's local debugging connection, with port 9222 mentioned in troubleshooting guidance.

## Setup and configuration

The documented installation command uses Node Package Manager and the `comet-mcp` package:

```json
{
  "mcpServers": {
    "comet-bridge": {
      "command": "npx",
      "args": ["-y", "comet-mcp"]
    }
  }
}
```

Node.js 18 or newer, Perplexity Comet, and an MCP client are required. The README specifically demonstrates configuration for Claude Code and states that other MCP clients can be used. Comet must also be installed locally. On macOS and native Windows, the server detects the standard Comet installation locations. A nonstandard installation can be selected with the `COMET_PATH` environment variable.

Supported platforms are macOS, Windows, and WSL2. WSL2 needs mirrored networking so the Linux environment can reach Comet running on Windows. The README recommends enabling this in `.wslconfig` and restarting WSL before use.

## Tools and capabilities

The hanzili/comet-mcp MCP server exposes six tools:

- `comet_connect` establishes the browser connection and can launch Comet.
- `comet_ask` submits a task and waits for its response.
- `comet_poll` checks the status of a task that is still running.
- `comet_stop` stops the current task.
- `comet_screenshot` captures the current page.
- `comet_mode` changes Comet's mode among `search`, `research`, `labs`, and `learn`.

Together, these tools support both short requests and longer research operations where the client needs to poll for completion.

## Limitations and notes

The server depends on the locally installed Perplexity Comet browser; it does not provide an independent web browser or replace Comet. Availability therefore depends on Comet starting correctly and accepting a remote debugging connection. If the connection fails, the README recommends checking the platform-specific installation path and whether port 9222 is available.

WSL2 users may need additional network configuration, and clients may need to be restarted after MCP configuration changes. The provided material does not describe API-key configuration, hosted deployment, or support for platforms beyond macOS, Windows, and WSL2.

_Full upstream README: https://allmcps.com/mcp/hanzili-comet-mcp/readme_