Log inSubmit server
Comet MCP logo

Comet MCP

by hanzili

Delegates web browsing and research tasks to Perplexity Comet through MCP, with progress tracking and screenshots.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Comet MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hanzili-comet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "comet-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y comet-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The hanzili/comet-mcp MCP server connects an MCP client to the Perplexity Comet browser for delegated web browsing and research. It uses Chrome DevTools Protocol to send high-level tasks to Comet, monitor long-running work, stop tasks, capture pages, and change Comet modes. Reach for it when an agent needs dynamic websites, login flows, navigation, or research beyond static search results. It runs locally through Node.js and can automatically start Comet when required.

Use cases

  • Delegate deep web research to Comet
  • Monitor long-running browser tasks
  • Navigate login-protected websites
  • Capture the current browser page
  • Switch between Comet research modes

Key features

  • Perplexity Comet browser bridge
  • Task submission and response waiting
  • Progress polling for long-running tasks
  • Task cancellation
  • Page screenshots
  • Search, research, labs, and learn modes

Tools6

What Comet MCP lets your agent do. Expand a tool for its parameters.

Self-reported~64 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · comet-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars180Stargazers on the source repository.
npm downloads413Package downloads in the last 30 days.
Last commit9mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed6Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Comet MCP works

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:

config.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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Comet MCP

Add an MCP server entry that runs `npx -y comet-mcp`, then install Perplexity Comet locally.

You need Node.js 18 or newer, Perplexity Comet, and an MCP client. Supported platforms are macOS, Windows, and WSL2.

The README demonstrates Claude Code and says the server works with any MCP client, but it does not specifically document Claude Desktop.

Set the `COMET_PATH` environment variable to the installed Comet executable or application path.

WSL2 requires mirrored networking so the Linux environment can connect to Comet running on Windows.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewComet MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hanzili-comet-mcp?style=directory)](https://allmcps.com/mcp/hanzili-comet-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/hanzili-comet-mcp"><img src="https://allmcps.com/api/badge/hanzili-comet-mcp?style=directory" alt="Comet MCP on AllMCPs" /></a>