
How to add comet-mcp to Cursor
Give Claude Code a browser that thinks — delegate agentic web browsing and deep research to Perplexity Comet. Paste the config into ~/.cursor/mcp.json and restart Cursor.
Last updated June 14, 2026 · 159★ · stdio · no auth
Cursor config for comet-mcp
{
"mcpServers": {
"comet-mcp": {
"command": "npx",
"args": [
"-y",
"comet-mcp"
]
}
}
}Setup steps
- 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
- 2Paste the comet-mcp config below into the "mcpServers" object.
- 3Fill in placeholder secrets, then save.
- 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
- 5Ask Cursor to use one of comet-mcp's tools to confirm it's connected.
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 Cursor
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 + Cursor FAQ
Where is the Cursor config file?
Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the comet-mcp config there under the "mcpServers" key and restart the client.
Is comet-mcp safe to use with Cursor?
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.