Skip to main content
Glama
Sign In
Perplexity Comet MCP

Perplexity Comet MCP

by RapierCraft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Perplexity Comet MCP

No user-submitted related servers found.

    Related Servers

    • Comet MCP Server

      AdilShaikh1
      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

    • Comet MCP

      hanzili
      A
      license
      A
      quality
      D
      maintenance
      Connects 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.
      6
      76 npm
      181
      MIT

    • comet-mcp

      simplicianokelly52
      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
      76 npm
      MIT

    • firefox

      llyfn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to drive your everyday logged-in browser session — opening and closing tabs, navigating, clicking, typing, scrolling, filling forms, uploading files, taking screenshots, and reading page text, console output and network requests. It runs through a local native-messaging bridge, scoping each client session to its own window behind yours.
      216 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose: connect, send request, manage tabs, take screenshot, etc. No two tools overlap in function, so an agent can easily select the appropriate one.

    Naming Consistency5/5

    All tools follow the consistent pattern 'comet_<verb>', using lower_snake_case with clear verbs (ask, connect, mode, etc.), making naming predictable and intuitive.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a browser agent. It covers essential actions without unnecessary bloat, balancing comprehensiveness and simplicity.

    Completeness4/5

    The tool set covers core workflows: connecting, browsing (via ask), mode switching, tab management, screenshot capture, file upload, and stopping agents. Minor gaps like explicit URL navigation might exist but are likely handled by comet_ask.

    Maintenance

    ActivityInactive
    ResponsivenessUsually handled

    Resources