Perplexity Comet adds local MCP to bridge web and desktop files

Most AI browsers today hit a hard wall the second they try to interact with your physical computer. They can scrape websites, fill out online forms, and write emails, but ask them to grab a screenshot sitting on your desktop, and they freeze.

Perplexity seems ready to bridge that gap. According to details spotted in development builds by TestingCatalog, the company is preparing to add local Model Context Protocol (MCP) support to its Comet browser.

Reaching beyond the browser sandbox

Comet already supported remote MCPs for connecting to cloud services. The big shift here is bringing local MCPs into the mix, which effectively links the browser's automation engine directly to your local operating system.

With local MCP integration, Comet can theoretically access your local folders, inspect files, and trigger desktop applications through simple natural language prompts.

Take social media as an everyday example. If you ask Comet to draft and post an update on X, it could soon pull an image stored on your local drive and attach it automatically. That solves one of the most frustrating bottlenecks in current web-only agent workflows.

TestingCatalog notes that the feature is still baking in internal builds, so there is no guarantee that full capabilities like direct file uploads will be completely active upon launch. But its presence makes Perplexity's direction clear: turning Comet into a universal agent workspace that blurs the boundary between web browsing and local desktop tasks.

Why it matters

We think this is the exact upgrade AI browsers need to become genuine daily drivers for power users. Web automation is great, but real work almost always involves local assets, spreadsheets, and files. Unlocking local MCP access makes Comet significantly more capable than standard AI search wrappers.

Across the industry, this moves the goalposts. While competitors are still fine-tuning sidebar summaries, Perplexity is pushing toward system-level desktop automation. If this catches on, rival browsers will have no choice but to follow suit with their own local agent protocols.

That said, giving a web agent permission to touch local folders creates an obvious trust dilemma. How do you stop a compromised prompt from rifling through sensitive files? We believe Perplexity's next critical challenge won't just be adding more tools, but building clear permission guardrails and centralized oversight so users actually feel safe letting Comet roam their hard drives.