general MCP Server
MCP Server connecting to Perplexity Comet browser
Discovered via unknown and last synced 3mo ago.
1. Install the package
npx comet-mcp
2. Add to claude_desktop_config.json
{
"mcpServers": {
"comet-mcp": {
"command": "npx",
"args": [
"comet-mcp"
]
}
}
}Config file location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows)
AI application developers and researchers who need real-time web browsing capabilities integrated into Claude-based workflows. Product teams building AI assistants that require current information, fact-checking, or dynamic content retrieval will benefit from seamless Perplexity Comet integration without context switching.
Fetch current web data directly within Claude interactions to answer questions about live events, recent news, or trending topics without relying on training data cutoffs.
Validate claims and retrieve authoritative sources by accessing live search results, enabling more reliable and trustworthy AI-generated responses.
Create autonomous agents that can research topics, gather competitive intelligence, or monitor specific web content as part of automated workflows.
Supplement retrieval-augmented generation systems with real-time web search to combine static knowledge bases with current information.
The MCP server acts as a bridge between Claude and Perplexity's Comet browser, exposing web browsing capabilities through the Model Context Protocol. This allows Claude to execute searches and retrieve live web content as part of its reasoning process.
Latency depends on Perplexity's search infrastructure and network conditions, but typical search queries should resolve within a few seconds. For time-sensitive applications, consider caching results or implementing request batching.
Control depends on the Comet browser's configuration. Most constraints would be configured at the Comet instance level rather than through the MCP server itself. Check Perplexity's documentation for available access controls.
Rate limits would be determined by your Perplexity Comet instance configuration. You should monitor usage patterns in development and plan for throttling if deploying to production with high query volumes.
Capture current page
Description
Check progress on long-running tasks
Send a task and wait for response
Switch modes: search, research, labs, learn
Connect to Comet (auto-starts if needed)
Stop current task