Brave Leo AI with Real-Time Search & MCP vs Comet Browser by Perplexity AI

“The primitive here is MCP client support baked into the browser sidebar — not a plugin, not an extension, the browser itself speaks MCP. The DX bet is that developers already have MCP servers running locally (which, post-Claude Desktop explosion, a surprising number do), so Brave is a zero-config client for them. The first-10-minutes test actually holds up: point Leo at your local MCP server, no API keys, no separate app install. The weekend-alternative comparison is real though — Claude Desktop does this already and has a bigger ecosystem. What earns the ship is that this is infrastructure-level integration, not a feature flag, and the real-time search grounding means you're not stuck with stale context.”

“Category: browser-native AI assistant with MCP support. Direct competitor is Claude Desktop for MCP workflows and Arc with its AI features for browser-integrated AI. The specific scenario where this breaks is enterprise MCP server setups — Leo's permission model and how it handles remote MCP servers with sensitive credentials is not clearly documented, and that will stop adoption dead in any team environment. What kills this in 12 months isn't a competitor — it's Chrome shipping Gemini with MCP support natively, which Google has every incentive to do given their MCP investments. What earns the ship anyway is that Brave has real distribution (millions of daily users), real-time search is table stakes that Leo was missing, and MCP support here is genuinely first-mover for a browser. To be wrong about the ship: Google has to ship Chrome AI with MCP before Brave builds meaningful workflow lock-in.”

“The category is agentic browser automation — direct competitors are Anthropic's Computer Use, OpenAI Operator, and Arc's now-shelved Browse for Me, all of which have demonstrated the same core loop and hit the same walls: form auth, CAPTCHAs, and any site that detects non-human behavior. Comet breaks the moment a user wants it to handle a logged-in, dynamic SPA that rate-limits bots — which is most of the web that matters. What kills this in 12 months: OpenAI ships Operator to all ChatGPT users for free and Perplexity's differentiation collapses to brand preference. To earn a ship, Comet needs to demonstrate persistent session handling and a credible story for the 60% of high-value tasks that live behind auth walls.”

“The thesis: in 2-3 years the browser is the primary MCP client for most non-developer users, because it's the ambient computing surface they already live in — not a dedicated app, not a terminal. This is a falsifiable bet that requires MCP adoption to continue accelerating outside of developer toolchains and into consumer workflows. The second-order effect that isn't obvious: if Leo becomes a credible MCP client, Brave gains leverage over which MCP servers get adopted, because discoverability flows through the browser. The trend line is MCP standardization as the USB-C of AI tool connectivity — Brave is early here, not on-time, and the window before Chrome absorbs this is maybe 18 months. The future state where this is infrastructure: Leo is the default orchestration layer for personal productivity MCP servers the way the browser is the default HTTP client.”

“The thesis here is specific and falsifiable: by 2027, the browser tab is no longer a viewport you stare at — it's a task queue you delegate to. Comet is betting that the interface layer between humans and the web collapses from 'navigate and click' to 'state intent and verify result.' That's a real trajectory, and Perplexity is one of the few players with a live search index plus the intent-capture surface to make the delegation model feel natural rather than scripted. The second-order effect that matters: if Comet works, SEO as a discipline dies faster than anyone is modeling — the bot reads the page so the human doesn't, and click-through becomes irrelevant. The dependency that has to hold: users must be willing to hand over ambient browsing context to Perplexity's servers, which is a trust bet that sits on regulatory quicksand. Still, as a positioned bet on the trend of intent-first computing, this is early and credible rather than late and derivative.”

“The job-to-be-done here is actually two separate jobs stapled together: 'answer questions with current information' (real-time search) and 'automate tasks via connected tools' (MCP). That 'and' is a focus problem — neither job is done completely enough to replace its current solution. Onboarding for the MCP piece requires the user to already know what an MCP server is, find one, configure the connection, and understand what Leo can do with it — that's not under 2 minutes, that's a tutorial for a developer audience. Real-time search grounding is the more complete feature and should have been the standalone launch. What would need to change: separate the two capabilities, get real-time search to reliably beat Perplexity for browser-based research, and build an MCP server directory inside the browser so non-developers can actually use the tool-calling feature.”

“The job-to-be-done as stated is 'complete multi-step web tasks autonomously' — that sentence contains an 'and' hiding inside 'multi-step,' which means this product is trying to solve task delegation, context retention, and web navigation simultaneously before nailing any one of them. The onboarding reality: users join a waitlist, get access inside a Pro subscription, and then face the blank-slate problem of not knowing which tasks are reliably automatable versus which will silently fail halfway through. That's not a 2-minute path to value — that's a discovery tax. The product isn't complete enough to replace any existing workflow today because there's no task library, no failure transparency, and no way to audit what the agent actually did. Until Comet ships a defined set of tasks it handles end-to-end with high reliability and surfaces that clearly at onboarding, it's a demo with a waitlist, not a product.”

“The buyer is a Perplexity Pro subscriber who already pays $20/month — Comet is a retention and upgrade mechanism dressed as a product launch, which is actually smart distribution. The moat question is harder: browser distribution is a graveyard (ask Opera, Brave, Arc) and the switching cost of a browser is enormous for consumers but thin for Perplexity because users won't abandon Chrome for search features alone. The business survives model cost compression because Perplexity's value isn't the underlying LLM — it's the index and the task orchestration layer sitting on top of it. What worries me is the expand story: once you've automated the tasks a Pro user cares about, what's the upsell? There's no obvious enterprise tier with audit logs and admin controls mentioned at launch, which means the revenue ceiling is whatever the Pro subscriber count is. Viable, but not yet a standalone business thesis.”