M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
C

Comet MCP

Community
Give Claude Code a browser that thinks.
How to install ↓ Compare GitHub source repository ↗
Category
Browser #15 of 32
Stars
★ 181 Popular
Transport
stdio (local process)
Runtime
Node.js 18+
Credentials
No credential needed
License
MIT
Last commit
⚠
Tools
6
54FMRS · D

This server offers a multi-agent delegation browsing approach, combining Claude's coding intelligence with Perplexity's web intelligence, but requires additional installation of Comet browser and carries certain security and privacy risks.

Strongest · Setup experience 13/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
10/20
Maintenance
11/20
Documentation
12/20
Setup experience
13/20
Why each score
Reliability 8/20
Did not execute code, but inspected source files. Server uses Node.js/TypeScript and connects to Comet browser via CDP. Init and tool-list handshake logic clear, but error handling and edge cases (e.g., browser not started, port conflict) not thoroughly tested. Since no committed tests and CI workflow, reliability max 12, conservative 8.
Security and permissions 10/20
No malicious code or credential leakage found. Tools limited to browser control, no high-risk operations like file system or remote command execution. But lack confirmation for dangerous operations and no data-flow disclosure (e.g., data sent to Perplexity). Security score moderate, not red-line.
Maintenance 11/20
Repo has 167 stars, 7 open issues, not archived. MIT license present. But no release/commit history provided, and no security response policy. Maintenance score moderate-low.
Documentation 12/20
README provides installation, config, usage examples, and troubleshooting. But missing detailed tool parameters and cost/limits. Documentation not supported by verifiable evidence (tests or CI). Quality okay but gaps.
Setup experience 13/20
README provides clear steps including Claude Code config and Comet browser installation. But depends on external Comet browser and specific network config (e.g., WSL), so setup may be environment-limited. Since no tests or CI verification, setup score max 15, conservative 13.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

  • Developers needing deep web research and interactive browsing
  • Users who want to delegate browsing to a specialized AI
  • Tasks involving dynamic content or login walls

Not for

  • Simple queries that don't require complex browser interaction
  • Users who don't install Comet browser
  • Users who need low-level control of the browser

Required permissions

  • Auto-launch Comet browser
  • Communicate with browser via CDP
  • Read and write browser page content
  • Requires Node.js 18+ environment

Risks and side effects

  • Browser automation may pose security risks; ensure trust in the source
  • Comet browser may collect usage data; consider privacy
  • Auto-launching browser may consume system resources

Setup

Before you start

Runtime：Node.js 18+

Other optional settings (1)
COMET_PATH optional Custom path to the Comet browser executable; only needed if Comet is not installed in its default location.
  1. Add the configuration above to ~/.claude.json or .mcp.json.
  2. Install Perplexity Comet browser (download from official site).
  3. Restart Claude Code after configuration.

If Comet is installed in a non-standard location, set the COMET_PATH environment variable.

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

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "comet-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "comet-mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add comet-bridge -- npx -y comet-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After configuring and restarting Claude Code, tools like comet_connect and comet_ask should appear in the tool list; running comet_connect and successfully connecting to the Comet browser confirms the install works.

Troubleshooting

  1. Cannot connect to Comet: Check if Comet is installed (macOS: /Applications/Comet.app, Windows: %LOCALAPPDATA%\Perplexity\Comet\Application\)
  2. WSL cannot connect: Enable mirrored networking or use Windows PowerShell
  3. Tools not showing: Restart Claude Code

Things to try

Once connected, you can ask your AI assistant things like:

  • Use Comet to research the top AI frameworks in 2025
  • Log into my GitHub and check my notifications
  • Take a screenshot of the current page
  • Switch Comet to research mode

Tools 6

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

Use cases

Research top AI frameworks in 2025.
Log into GitHub and check notifications.

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

Comet MCP is an MCP server that connects Claude Code to the Perplexity Comet browser. It delegates browsing tasks to an AI purpose-built for web research and browsing, allowing Claude to focus on coding. It supports deep research, real-time task monitoring, and multiple modes.

Similar servers

Compare with other MCP servers

Source revision 6f10c86b0991 Data synced 2026-10-11 Read the FMRS scoring method