comet-mcp

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.

Why?

Existing web tools for Claude Code fall short:

• WebSearch/WebFetch only return static text - no interaction, no login, no dynamic content
• Browser automation MCPs (like browser-use) are agentic but use a generic LLM to control a browser - less polished, more fragile

Comet is Perplexity's native agentic browser - their AI is purpose-built for web research, deeply integrated with search, and battle-tested. Give it a goal, it figures out how to get there.

comet-mcp bridges Claude Code and Comet: Claude's coding intelligence + Perplexity's web intelligence.

Quick Start

1. Configure Claude Code

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

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

2. Start Comet Browser

Download Perplexity Comet and launch with remote debugging:

# macOS
/Applications/Comet.app/Contents/MacOS/Comet --remote-debugging-port=9222

3. Use in Claude Code

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

Tools

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

Architecture

Claude Code <-> MCP <-> comet-mcp <-> CDP <-> Comet Browser <-> Perplexity AI

Requirements

• Node.js 18+
• Perplexity Comet Browser
• Claude Code (or any MCP client)

Troubleshooting

"Cannot connect to Comet"

• Make sure Comet is running with --remote-debugging-port=9222
• Check if port 9222 is available

"Tools not showing in Claude"

• Restart Claude Code after config changes

License

MIT

---

Report Issues · Contribute