comet-mcp
Related Servers
Alternatives to comet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceConnects Claude to Perplexity Comet's agentic browser for autonomous web browsing, deep research, and real-time task monitoring. Enables Claude to delegate web research tasks and receive comprehensive results through multiple browsing modes.663 npm180MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude to perform web searches using Perplexity's API with intelligent model selection based on query intent and support for domain and recency filtering.64MIT
- 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
- AlicenseAqualityDmaintenanceMCP server that enables Claude to request chat completions with citations from the Perplexity API.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to perform web searches on Perplexity.ai using browser automation instead of an official API. It supports persistent authenticated sessions and returns search results along with cited sources directly to the client.336 npm10MIT
TDQS
Scored across 8 tools
Most tools have distinct purposes, but 'comet_ask' and 'comet_poll' could cause confusion as both relate to agentic tasks. 'comet_ask' initiates a task, while 'comet_poll' monitors it, which might lead to misselection if an agent misunderstands their roles. Otherwise, tools like 'comet_folders', 'comet_library', and 'comet_screenshot' are clearly differentiated.
All tools follow a consistent 'comet_' prefix with snake_case naming, such as 'comet_ask', 'comet_connect', and 'comet_folders'. This predictable pattern makes it easy for agents to identify and use the tools without confusion, enhancing usability across the set.
With 8 tools, the count is well-scoped for a Comet/Perplexity integration server. Each tool serves a specific function, from connection and mode switching to research management and task control, without feeling bloated or insufficient for the domain's needs.
The tool set covers core workflows like connecting, querying, managing research, and controlling tasks, but there are minor gaps. For example, no tool explicitly handles disconnecting from Comet or clearing/resetting sessions, which agents might need for robust operation. However, the existing tools support most essential interactions effectively.