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.
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.
Add to ~/.claude.json or .mcp.json:
{
"mcpServers": {
"comet-bridge": {
"command": "npx",
"args": ["-y", "comet-mcp"]
}
}
}Download and install Perplexity Comet.
That's it! The MCP server will automatically launch Comet with remote debugging enabled when needed. If Comet is already running, it will restart it with the correct flags.
You: "Use Comet to research the top AI frameworks in 2025"
Claude: [connects to Comet, delegates research, monitors progress, returns results]
| 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 |
Claude Code <-> MCP <-> comet-mcp <-> CDP <-> Comet Browser <-> Perplexity AI
"Cannot connect to Comet"
- Make sure Comet is installed at
/Applications/Comet.app - Check if port 9222 is available (no other Chrome/debugger using it)
"Tools not showing in Claude"
- Restart Claude Code after config changes
MIT