Delegate web research from Claude Code to Comet
Give Claude Code a browser that thinks. Task: 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 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: 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 Tools How It Works Claude sends high-level goals ("research X", "log into Y"). Comet figures out the clicks, scrolls, and searches. Results flow back to Claude. Requirements Node.js 18+ Perplexity Comet Browser Claude Code (or any MCP client) Supported platforms: macOS, Windows, WSL2 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: Enable mirrored networking (one-time setup): # Create/edit %USERPROFILE%\.wslconfig (Windows side) [wsl2] networkingMode=mirrored Enable mirrored networking (one-time setup): Restart WSL: wsl --shutdown # Then reopen your WSL terminal Restart WSL: That's it! Comet MCP auto-detects WSL and uses PowerShell to communicate with Windows. 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: 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; tools: Claude Code, Perplexity Comet. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include Node.js 18+, Perplexity Comet installed, and Claude Code. WSL2 requires mirrored networking configuration. The tool relies on Comet's availability and correct path detection. Source reliability is secondary (GitHub README); no independent verification of performance or stability is provided. Human approval is implied for sensitive actions like logging into accounts..
Tools
Published on Agent Work Atlas:
Overview
Give Claude Code a browser that thinks.
Workflow
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 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: 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 Tools How It Works Claude sends high-level goals ("research X", "log into Y"). Comet figures out the clicks, scrolls, and searches. Results flow back to Claude. Requirements Node.js 18+ Perplexity Comet Browser Claude Code (or any MCP client) Supported platforms: macOS, Windows, WSL2 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: Enable mirrored networking (one-time setup): # Create/edit %USERPROFILE%\.wslconfig (Windows side) [wsl2] networkingMode=mirrored Enable mirrored networking (one-time setup): Restart WSL: wsl --shutdown # Then reopen your WSL terminal Restart WSL: That's it! Comet MCP auto-detects WSL and uses PowerShell to communicate with Windows. 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: 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
Reported result
Actual outcomes are not reported in the source; it only claims a conceptual result of combining Claude's coding intelligence with Perplexity's web intelligence. No metrics, success rates, or failure cases are provided. Proposed acceptance check: Verify that a simple query like "research top AI frameworks" returns structured text from Comet without requiring manual browser interaction.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include Node.js 18+, Perplexity Comet installed, and Claude Code. WSL2 requires mirrored networking configuration. The tool relies on Comet's availability and correct path detection. Source reliability is secondary (GitHub README); no independent verification of performance or stability is provided. Human approval is implied for sensitive actions like logging into accounts.
Try it
I want to test the Comet MCP integration for web research. First, ensure Node.js 18+ and Perplexity Comet are installed on my [macOS/Windows] machine. Add the following to my ~/.claude.json: {"mcpServers": {"comet-bridge": {"command": "npx", "args": ["-y", "comet-mcp"]}}}. Restart Claude Code. Then, ask Claude to "Use Comet to research the top 3 open-source LLM frameworks in 2025". Monitor if Comet launches automatically. If it fails, check if port 9222 is free or if WSL2 networking is mirrored. Do not proceed to complex tasks like logging into GitHub until this simple search works. Show me the raw output from Comet before summarizing. If the connection fails, stop and report the error message.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.