MCP Server connecting to Perplexity Comet browser
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"comet-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server that connects Claude Code to Perplexity Comet - enabling agentic web browsing, deep research, and real-time task monitoring.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser / ai-ml
Persistent memory using a knowledge graph
Browser automation with Puppeteer for web scraping and testing
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for Comet Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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 into two categories, both with limitations:
Return static text. No interaction, no login, no dynamic content. Great for quick lookups, but can't navigate complex sites or fill forms.
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.
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.
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 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.
Works out of the box. Comet MCP auto-detects Windows and launches Comet from its default install location.
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
Restart WSL:
wsl --shutdown
# Then reopen your WSL terminal
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.
If Comet is installed in a non-standard location:
{
"mcpServers": {
"comet-bridge": {
"command": "n
... [View full README on GitHub](https://github.com/hanzili/comet-mcp#readme)