Skip to main content
Glama

Related Servers

Alternatives to Comet MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Gives 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.
      11
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Bridges 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.
      8
      113 npm
      50
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      8
      63 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Integrates 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 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive