MCP Directory

How to add comet-mcp to Claude Desktop

Give Claude Code a browser that thinks — delegate agentic web browsing and deep research to Perplexity Comet. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 159★ · stdio · no auth

Claude Desktop config for comet-mcp

{
  "mcpServers": {
    "comet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "comet-mcp"
      ]
    }
  }
}

Setup steps

  1. 1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
  2. 2Paste the comet-mcp config below under the top-level "mcpServers" key.
  3. 3Fill in any placeholder secrets (API keys, paths) in the snippet.
  4. 4Save the file, then fully quit and reopen Claude Desktop.
  5. 5Open a chat and confirm comet-mcp's tools appear under the 🔌 tools menu.

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 Claude Desktop

comet_connect

Connect to Comet (auto-starts the browser if needed).

comet_ask

Send a task to Comet and wait for the response.

comet_poll

Check progress on long-running tasks.

comet_stop

Stop the current task.

comet_screenshot

Capture the current page.

comet_mode

Switch 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 + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the comet-mcp config there under the "mcpServers" key and restart the client.

Is comet-mcp safe to use with Claude Desktop?

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.

View repo Full comet-mcp page