MCP

3 items

Engadget / Wired 2026-03-15-1

NVIDIA NemoClaw: Open-Source Enterprise Agent Platform

NVIDIA's NemoClaw applies the CUDA playbook to agents: make the orchestration layer free and hardware-agnostic, then let silicon pull-through follow. The decisive question isn't capability but MCP compatibility — if NemoClaw speaks MCP, NVIDIA becomes the enterprise runtime for the existing ecosystem; if not, they're forking the standard.

Databricks 2026-03-13-2

Databricks Genie Code: Platform Incumbents Build Agent Moats

Databricks launches Genie Code as the "don't leave the platform" response to Claude Code and Codex eating data engineering workflows. The internal benchmark (77.1% vs 32.1%) is marketing, but the structural argument holds: native catalog/lineage/governance integration provides context that MCP-level API access can't replicate. The real story is the simultaneous Quotient AI acquisition — buying the eval→RL production loop from the team that built GitHub Copilot's quality infrastructure. The most differentiated feature (autonomous background agents) ships as "coming soon" vaporware.

GitHub 2026-03-13-3

Agent Browser Protocol: Chromium Fork That Makes Browsing a Step Machine for LLM Agents

ABP solves the fundamental impedance mismatch between async browser state and synchronous LLM reasoning by forking Chromium itself — freezing JS execution and virtual time between agent steps so the page literally waits for the model. At 90.5% on Mind2Web, this is the strongest signal yet that browser agents need engine-level integration, not another CDP wrapper. The MCP-native interface (REST + MCP baked into the browser process) is the right abstraction layer, but the Chromium fork dependency is a distribution bottleneck that will matter at scale.