Brave Leo AI with Real-Time Search & MCP vs Glean Agents Platform

“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.”

“The primitive here is a hosted agent runtime that uses Glean's search index as a retrieval layer and exposes workflow triggers — essentially a RAG-grounded agent builder with pre-built connectors. The DX bet is that enterprises want a no-code/low-code surface rather than composable APIs they can wire into their own stack, which is probably the right call for the buyer but makes this nearly useless if you want to integrate it into an existing internal toolchain. The moment of truth — can a developer get an agent running against real company data in under 30 minutes — is entirely gated behind the sales cycle and enterprise provisioning, which means there's no public hello-world to evaluate. The blog post has no repo, no public API docs, no sandbox, and no pricing: three red flags for any tool claiming to serve builders.”

“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 direct competitors here are ServiceNow's Now Assist, Microsoft Copilot Studio, and Salesforce Agentforce — all of which have massive distribution advantages. Where Glean actually earns its place is the knowledge layer: if you've already got Glean indexing your company's internal content with real permissions, building agents on top of that foundation is meaningfully different from a blank-slate agent builder. The scenario where this breaks is large enterprises with fragmented IT budgets, where Glean has to compete against the existing Microsoft 365 or ServiceNow contract rather than supplement it. What kills this in 12 months isn't a competitor — it's Microsoft bundling Copilot Studio capabilities deeper into M365 E5 licenses and making the 'we already have Glean' argument harder to close.”

“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 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 is precise: 'help enterprise employees get answers and trigger actions using company knowledge without requiring IT to build custom integrations from scratch.' That's a real, well-scoped problem. The completeness question is where Glean has an edge over blank-slate agent builders — because the knowledge indexing is already done for existing Glean customers, the activation cost for the first useful agent should be low compared to starting from Copilot Studio with an empty SharePoint. The gap I'd flag is that 'over 100 business apps' is a connector count, not a measure of integration depth — the real test is whether an agent can reliably take action in Salesforce or ServiceNow, not just read from them, and nothing in the GA announcement quantifies that reliability at scale.”

“The buyer here is the CIO or VP of IT, pulling from digital transformation or enterprise AI budget — not a departmental line item. Glean's smart move is that the Agents Platform is an expansion motion inside an existing Glean contract, not a net-new sale, which is the only land-and-expand story that actually works. The moat is real but narrow: it's the indexed, permissioned knowledge graph that takes months to build and tune per enterprise, creating genuine switching costs. The stress test is whether enterprises will consolidate on one platform player — if Microsoft or Salesforce offers 80% of this functionality bundled into existing spend, Glean's standalone value proposition compresses fast unless they keep the knowledge indexing quality visibly ahead.”