comet-mcp
Give Claude Code a browser that thinks — delegate agentic web browsing and deep research to Perplexity Comet.
Add to your client
Copy the config for your MCP client and paste it into its config file.
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"comet-mcp": {
"command": "npx",
"args": [
"-y",
"comet-mcp"
]
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Node.js 18+
- Perplexity Comet browser installed (macOS: /Applications/Comet.app; Windows: %LOCALAPPDATA%\Perplexity\Comet\Application\)
- Claude Code or any MCP client
- Supported platforms: macOS, Windows, WSL2 (WSL2 requires mirrored networking)
About comet-mcp
comet-mcp bridges Claude Code to the Perplexity Comet browser, letting Claude delegate web browsing and deep research to Comet rather than driving a browser itself. Claude sends high-level goals and Comet figures out the clicks, scrolls, and searches, returning results — keeping Claude's context focused on coding while Perplexity handles web intelligence. The pipeline is: Claude Code -> MCP Server -> CDP -> Comet Browser -> Perplexity AI.
Tools & capabilities (6)
comet_connectConnect to Comet (auto-starts the browser if needed).
comet_askSend a task to Comet and wait for the response.
comet_pollCheck progress on long-running tasks.
comet_stopStop the current task.
comet_screenshotCapture the current page.
comet_modeSwitch Comet modes: search, research, labs, learn.
What this server can do
comet-mcp provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Delegate deep web research to Comet (e.g. 'research the top AI frameworks in 2025') while Claude stays focused on coding.
- Have Comet handle login walls and authenticated navigation (e.g. 'log into my GitHub and check my notifications').
- Navigate complex sites and dynamic content that static search APIs (Tavily, WebFetch) can't handle.
- Monitor long-running browsing tasks in real time via polling.
- Capture screenshots of the current page during a browsing session.
Security notes
The server launches the local Comet browser with remote debugging on port 9222 and drives it via the Chrome DevTools Protocol. Tasks delegated to Comet can navigate authenticated sites and handle login flows using the browser's existing sessions, so it has access to whatever the local Comet browser can reach.
comet-mcp FAQ
How is this different from Puppeteer/Playwright MCP or browser-use?
Those use a one-agent-do-all approach where the coding model also decides where to click and type, which overwhelms the context window. comet-mcp instead delegates browsing to Perplexity Comet, an AI purpose-built for web research, so Claude stays focused on coding.
Do I need a Perplexity API key?
No. The server connects to a locally-installed Comet browser over CDP; there is no API key configuration shown in the docs.
How does the server reach Comet?
It communicates with the local Comet browser via the Chrome DevTools Protocol (CDP) on port 9222 and auto-launches Comet with remote debugging when needed.
What if Comet is installed in a non-standard location?
Set the COMET_PATH environment variable in the server config to point at your Comet install (e.g. env: { "COMET_PATH": "/path/to/your/Comet" }).
How do I run it under WSL2?
WSL2 requires mirrored networking. Set networkingMode=mirrored in %USERPROFILE%\.wslconfig on the Windows side, then run 'wsl --shutdown' and reopen WSL. The server auto-detects WSL and uses PowerShell to talk to Windows.
Alternatives to comet-mcp
Compare all alternatives →
All-in-one web access MCP — Web Unlocker, SERP, Scraper API, and a cloud Scraping Browser.
Popular community Playwright + API testing MCP server with codegen, screenshots, and device emulation.
Official Browserbase cloud-browser MCP built on Stagehand — natural-language act/extract/observe.