convez.ai
MCP ServerAutomaçãoIntermediário
hanzili

Comet MCP – Navegação Agentica com Perplexity

hanzili/comet-mcp

Navegação web inteligente e delegada para Claude Code

Ver no GitHub
BomPluginScore · de 0 a 100

MCP Server que conecta Claude Code ao Perplexity Comet, delegando tarefas de navegação web, pesquisa profunda e interação com páginas dinâmicas a um navegador de IA especializado. Em vez de Claude controlar o browser diretamente, o Comet assume a navegação enquanto Claude mantém o foco no código.

Instalação

$npx convez-ai hanzili/comet-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
181
Forks
33
Acompanhando
0
Saúde
57%
Último commit
há 10 meses
Versão
—
Issues abertas
14
Contribuidores
1

Casos de uso

  • Pesquisa profunda e síntese de informações na web
  • Automação de workflows que requerem login e navegação complexa
  • Monitoramento em tempo real de tarefas em páginas dinâmicas
  • Integração de inteligência web em pipelines de desenvolvimento

Veredito

Solução inovadora que separa responsabilidades: Claude raciocina sobre código, Comet raciocina sobre web. Reduz fragmentação de contexto e aproveita modelos especializados, mas requer Perplexity Comet instalado localmente e é mais pesado que APIs de busca simples.

README

A tradução para o português deste README ainda está na fila.

comet-mcp

npm version

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.

Demo

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

Quick Start

1. Configure Claude Code

Add to ~/.claude.json or .mcp.json:

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

2. Install Comet Browser

Download and install Perplexity Comet.

That's it! The MCP server automatically launches Comet with remote debugging when needed.

3. Use in Claude Code

You: "Use Comet to research the top AI frameworks in 2025"
Claude: [delegates to Comet, monitors progress, returns results]

You: "Log into my GitHub and check my notifications"
Claude: [Comet handles the login flow and navigation]

Tools

ToolDescription
comet_connectConnect to Comet (auto-starts if needed)
comet_askSend a task and wait for response
comet_pollCheck progress on long-running tasks
comet_stopStop current task
comet_screenshotCapture current page
comet_modeSwitch modes: search, research, labs, learn

How It Works

Claude Code  →  MCP Server  →  CDP  →  Comet Browser  →  Perplexity AI
   (reasoning)     (bridge)                              (web browsing)

Claude sends high-level goals ("research X", "log into Y"). Comet figures out the clicks, scrolls, and searches. Results flow back to Claude.

Requirements

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:

  1. Enable mirrored networking (one-time setup):

    # Create/edit %USERPROFILE%\.wslconfig (Windows side)
    [wsl2]
    networkingMode=mirrored
    
  2. Restart WSL:

    wsl --shutdown
    # Then reopen your WSL terminal
    
  3. That'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:

{
  "mcpServers": {
    "comet-bridge": {
      "command": "npx",
      "args": ["-y", "comet-mcp"],
      "env": {
        "COMET_PATH": "/path/to/your/Comet"
      }
    }
  }
}

Troubleshooting

"Cannot connect to Comet"

  • macOS: Ensure Comet is installed at /Applications/Comet.app
  • Windows: Comet should be in %LOCALAPPDATA%\Perplexity\Comet\Application\
  • Check if port 9222 is available

"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

License

MIT


Report Issues · Contribute

Ver o original no GitHub

Bom para

Relacionados