Comet MCP
Related Servers
Alternatives to Comet MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceConnects Claude Code to the Perplexity Comet browser to enable autonomous web browsing and agentic research. It features multi-tab management, smart completion detection, and a specialized tool set for organized information retrieval.8113 npm2-
- AlicenseAqualityDmaintenanceGives Claude a browser that thinks by connecting to Perplexity's Comet browser via Chrome DevTools Protocol, enabling AI-powered web search, navigation, reading, clicking, and screenshots while keeping Claude's context clean.112MIT
- AlicenseAqualityAmaintenanceBridges Claude with Perplexity's Comet browser for autonomous web browsing, research, and multi-tab workflow management. Supports dynamic content interaction, login wall handling, file uploads, and intelligent completion detection across Windows, macOS, and WSL platforms.8113 npm50MIT
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude to Perplexity Comet for agentic web browsing and deep research via an isolated browser instance. It enables Claude to delegate complex navigation, login flows, and real-time task monitoring to Perplexity's specialized research intelligence.863 npmMIT
- AlicenseNot gradedqualityDmaintenanceIntegrates the Sonar API to provide Claude with real-time web-wide research capabilities. Enables conversational web searches through Perplexity's AI-powered search engine for up-to-date information retrieval.1,255 npmMIT
- AlicenseAqualityCmaintenanceIntegrates Perplexity AI's search and research capabilities into Claude Code, enabling web-grounded answers, deep research, code review, and more with real-time citations.9102 npm2MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: comet_ask sends prompts, comet_connect establishes browser connection, comet_mode switches search modes, comet_poll checks status, comet_screenshot captures visuals, and comet_stop halts tasks. The descriptions clearly differentiate their functions, eliminating any ambiguity.
All tools follow a consistent 'comet_verb' naming pattern (e.g., comet_ask, comet_connect, comet_mode). This uniform prefix and snake_case structure make the set predictable and easy to understand, with no deviations in style or convention.
With 6 tools, the count is well-scoped for a browser/agent interaction server. Each tool serves a specific, necessary function in the workflow (e.g., connecting, querying, monitoring, controlling), and none feel redundant or missing for the domain's core operations.
The tool set covers essential CRUD-like operations for browser-based tasks: initiating (comet_connect), querying (comet_ask), configuring (comet_mode), monitoring (comet_poll), capturing (comet_screenshot), and stopping (comet_stop). A minor gap is the lack of a tool for direct page navigation or interaction beyond prompts, but agents can work around this using comet_ask for such actions.