comet

This MCP server, comet-bridge, connects Claude Code to Perplexity Comet to enable agentic web browsing, deep research, and task monitoring. It delegates web searching and browsing to Comet while Claude focuses on coding tasks, producing a collaborative flow where Comet handles navigation, logins, dynamic content, and long-running browsing tasks. The server exposes a set of tools that you can invoke from Claude Code to start a browsing session, submit research tasks, poll for progress, capture screenshots, and switch browsing modes. Tools include: comet_connect (start or connect to Comet), comet_ask (submit a task and wait for a response), comet_poll (check progress on long-running tasks), comet_stop (terminate the current task), comet_screenshot (capture the current page), and comet_mode (change modes such as search, research, labs, learn). By using Comet for the browsing layer, Claude can stay focused on reasoning and coding while obtaining robust web results and interactions through Comet’s interface.

Prerequisites:\n- Node.js 18+ (and npm) installed on your machine.\n- Claude Code (or any MCP client) configured to use MCP servers.\n- Perplexity Comet browser available to install and run.\n\nInstallation steps:\n1) Install Node.js 18+ from the official source if not already installed. Confirm with: node -v and npm -v.\n2) Install or run the Comet MCP server via npx as shown in the Quick Start:\n\nbash\n# Example local setup using the recommended MCP config\nnpx -y comet-mcp\n\n3) Configure Claude Code to point at the MCP server by adding the following to ~/.claude.json or .mcp.json:\n\njson\n{\n "mcpServers": {\n "comet-bridge": {\n "command": "npx",\n "args": ["-y", "comet-mcp"]\n }\n }\n}\n\n4) Ensure Perplexity Comet is installed and accessible. Installations may vary by platform; follow the Comet setup prompts when starting the MCP.\n5) Start Claude Code and load your MCP configuration. The MCP server will automatically launch Comet with remote debugging when needed.\n\nOptional: If Comet is installed in a non-standard location, you can specify COMET_PATH in the MCP config like so:\njson\n{\n "mcpServers": {\n "comet-bridge": {\n "command": "npx",\n "args": ["-y", "comet-mcp"],\n "env": {\n "COMET_PATH": "/path/to/your/Comet"\n }\n }\n }\n}\n

Tips and notes:\n- Ensure Node.js 18+ is running smoothly; some users may need to install build tools for native modules.\n- If you encounter "Cannot connect to Comet", verify Comet is installed at the expected path on macOS (/Applications/Comet.app) or Windows (%LOCALAPPDATA%\Perplexity\Comet\Application\).\n- WSL2 users with Windows should enable mirrored networking to allow communication between WSL and Windows-hosted Comet, following the guidance in the README.\n- You can customize the Comet path using COMET_PATH in the MCP config if your installation is non-standard.\n- After changing MCP config, restarting Claude Code is recommended to ensure tools appear and work correctly.\n- The npm package name for this server is comet-mcp. If you are embedding this in a larger workflow, you can reference the package name in automation scripts.\n- If you want to switch to a different integration flow (e.g., direct browser automation), you can explore other MCPs, but Comet MCP provides a delegation model that can improve context window efficiency for complex research tasks.