
How to add comet-mcp to Windsurf
Give Claude Code a browser that thinks — delegate agentic web browsing and deep research to Perplexity Comet. Paste the config into ~/.codeium/windsurf/mcp_config.json and restart Windsurf.
Last updated June 14, 2026 · 159★ · stdio · no auth
Windsurf config for comet-mcp
{
"mcpServers": {
"comet-mcp": {
"command": "npx",
"args": [
"-y",
"comet-mcp"
]
}
}
}Setup steps
- 1Open Windsurf → Cascade → the hammer/MCP icon → Configure (or edit ~/.codeium/windsurf/mcp_config.json).
- 2Paste the comet-mcp config below.
- 3Fill in placeholder secrets, then save.
- 4Click Refresh in the MCP panel.
- 5comet-mcp's tools become available to Cascade.
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)
What comet-mcp can do in Windsurf
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.
Security
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 + Windsurf FAQ
Where is the Windsurf config file?
Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Paste the comet-mcp config there under the "mcpServers" key and restart the client.
Is comet-mcp safe to use with Windsurf?
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.
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.