Comet Mcp

Created By
hanzili5 months ago
Overview

what is Comet Mcp?

Comet Mcp is an MCP server that connects Claude Code to Perplexity Comet, enabling agentic web browsing, deep research, and real-time task monitoring.

how to use Comet Mcp?

To use Comet Mcp, configure Claude Code with the MCP server settings, start the Comet Browser with remote debugging, and then use Claude Code to delegate research tasks to Comet.

key features of Comet Mcp?

  • Connects Claude Code to Perplexity Comet for enhanced web research.
  • Supports real-time task monitoring and progress checking.
  • Provides tools for capturing screenshots and switching modes for different tasks.

use cases of Comet Mcp?

  1. Researching AI frameworks and technologies.
  2. Monitoring web tasks in real-time.
  3. Automating web interactions for data gathering.

FAQ from Comet Mcp?

  • What is required to run Comet Mcp?

You need Node.js 18+, Perplexity Comet Browser, and Claude Code or any MCP client.

  • How do I troubleshoot connection issues?

Ensure Comet is running with the correct remote debugging port and check if the port is available.

  • Can I use Comet Mcp for any web research?

Yes, Comet Mcp is designed for deep web research and can handle various tasks.

Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
hanzili
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago