Comet MCP

1# comet-mcp
2 
3[![npm version](https://img.shields.io/npm/v/comet-mcp.svg)](https://www.npmjs.com/package/comet-mcp)
4 
5<a href="https://glama.ai/mcp/servers/@hanzili/comet-mcp">
6  <img width="380" height="200" src="https://glama.ai/mcp/servers/@hanzili/comet-mcp/badge" />
7</a>
8 
9**Give Claude Code a browser that thinks.**
10 
11An MCP server that connects Claude Code to [Perplexity Comet](https://www.perplexity.ai/comet) - enabling agentic web browsing, deep research, and real-time task monitoring.
12 
13![Demo](demo.gif)
14 
15## Why?
16 
17Existing web tools for Claude Code fall into two categories, both with limitations:
18 
19### 1. Search APIs (Tavily, Perplexity API, WebFetch)
20Return static text. No interaction, no login, no dynamic content. Great for quick lookups, but can't navigate complex sites or fill forms.
21 
22### 2. Browser Automation (browser-use, Puppeteer MCP, Playwright MCP)
23Can 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.
24 
25### 3. Comet MCP: Multi-Agent Delegation
26**Comet MCP takes a different approach.** Instead of Claude controlling a browser directly, it delegates to [Perplexity Comet](https://www.perplexity.ai/comet) - an AI purpose-built for web research and browsing.
27 
28- **Claude** stays focused on your coding task
29- **Comet** handles the browsing: navigation, login walls, dynamic content, deep research
30- **Result**: Claude's coding intelligence + Perplexity's web intelligence, working together
31 
32## Quick Start
33 
34### 1. Configure Claude Code
35 
36Add to `~/.claude.json` or `.mcp.json`:
37 
38```json
39{
40  "mcpServers": {
41    "comet-bridge": {
42      "command": "npx",
43      "args": ["-y", "comet-mcp"]
44    }
45  }
46}
47```
48 
49### 2. Install Comet Browser
50 
51Download and install [Perplexity Comet](https://www.perplexity.ai/comet).
52 
53That's it! The MCP server automatically launches Comet with remote debugging when needed.
54 
55### 3. Use in Claude Code
56 
57```
58You: "Use Comet to research the top AI frameworks in 2025"
59Claude: [delegates to Comet, monitors progress, returns results]
60 
61You: "Log into my GitHub and check my notifications"
62Claude: [Comet handles the login flow and navigation]
63```
64 
65## Tools
66 
67| Tool | Description |
68|------|-------------|
69| `comet_connect` | Connect to Comet (auto-starts if needed) |
70| `comet_ask` | Send a task and wait for response |
71| `comet_poll` | Check progress on long-running tasks |
72| `comet_stop` | Stop current task |
73| `comet_screenshot` | Capture current page |
74| `comet_mode` | Switch modes: search, research, labs, learn |
75 
76## How It Works
77 
78```
79Claude Code  →  MCP Server  →  CDP  →  Comet Browser  →  Perplexity AI
80   (reasoning)     (bridge)                              (web browsing)
81```
82 
83Claude sends high-level goals ("research X", "log into Y"). Comet figures out the clicks, scrolls, and searches. Results flow back to Claude.
84 
85## Requirements
86 
87- Node.js 18+
88- [Perplexity Comet Browser](https://www.perplexity.ai/comet)
89- Claude Code (or any MCP client)
90- **Supported platforms**: macOS, Windows, WSL2
91 
92## Windows & WSL Support
93 
94### Native Windows
95Works out of the box. Comet MCP auto-detects Windows and launches Comet from its default install location.
96 
97### WSL2 (Windows Subsystem for Linux)
98WSL2 requires **mirrored networking** to connect to Comet running on Windows:
99 
1001. **Enable mirrored networking** (one-time setup):
101   ```
102   # Create/edit %USERPROFILE%\.wslconfig (Windows side)
103   [wsl2]
104   networkingMode=mirrored
105   ```
106 
1072. **Restart WSL**:
108   ```bash
109   wsl --shutdown
110   # Then reopen your WSL terminal
111   ```
112 
1133. **That's it!** Comet MCP auto-detects WSL and uses PowerShell to communicate with Windows.
114 
115If mirrored networking isn't available, you'll see a helpful error message with setup instructions.
116 
117### Custom Comet Path
118If Comet is installed in a non-standard location:
119```json
120{
121  "mcpServers": {
122    "comet-bridge": {
123      "command": "npx",
124      "args": ["-y", "comet-mcp"],
125      "env": {
126        "COMET_PATH": "/path/to/your/Comet"
127      }
128    }
129  }
130}
131```
132 
133## Troubleshooting
134 
135**"Cannot connect to Comet"**
136- **macOS**: Ensure Comet is installed at `/Applications/Comet.app`
137- **Windows**: Comet should be in `%LOCALAPPDATA%\Perplexity\Comet\Application\`
138- Check if port 9222 is available
139 
140**"WSL cannot connect to Windows localhost"**
141- Enable mirrored networking (see WSL section above)
142- Or run Claude Code from Windows PowerShell instead of WSL
143 
144**"Tools not showing in Claude"**
145- Restart Claude Code after config changes
146 
147## License
148 
149MIT
150 
151---
152 
153[Report Issues](https://github.com/hanzili/comet-mcp/issues) · [Contribute](https://github.com/hanzili/comet-mcp)
154