MCP Server that gives Claude Code superpowers with Perplexity Comet browser - agentic web browsing, deep research, and real-time monitoring
npm install 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.
!Demo
Existing web tools for Claude Code fall into two categories, both with limitations:
- 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
Add to ~/.claude.json or .mcp.json:
``json`
{
"mcpServers": {
"comet-bridge": {
"command": "npx",
"args": ["-y", "comet-mcp"]
}
}
}
Download and install Perplexity Comet.
That's it! The MCP server automatically launches Comet with remote debugging when needed.
`
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]
`
| Tool | Description |
|------|-------------|
| comet_connect | Connect to Comet (auto-starts if needed) |comet_ask
| | Send a task and wait for response |comet_poll
| | Check progress on long-running tasks |comet_stop
| | Stop current task |comet_screenshot
| | Capture current page |comet_mode
| | Switch modes: search, research, labs, learn |
``
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.
- Node.js 18+
- Perplexity Comet Browser
- Claude Code (or any MCP client)
- Supported platforms: macOS, Windows, WSL2
1. Enable mirrored networking (one-time setup):
``
# Create/edit %USERPROFILE%\.wslconfig (Windows side)
[wsl2]
networkingMode=mirrored
2. Restart WSL:
`bash`
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.
json
{
"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\`"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
MIT
---