This month in Servo: new webview API, relative colors, canvas buffs, and more! - Servo aims to empower developers with a lightweight, high-performance alternative for embedding web technologies in applications.

Servo is becoming truly embeddable this year.

Firefox WebDriver Newsletter 145

WebDriver is a remote control interface that enables introspection and control of user agents. As such it can help developers to verify that their websites are working and performing well with all major browsers. The protocol is standardized by the W3C and consists of two separate specifications: WebDriver classic (HTTP) and the new WebDriver BiDi (Bi-Directional).

2026 Web Engines Hackfest

Web Platform community event for people working on the different engines (Chromium/Blink/V8, Safari/WebKit/JSC, Firefox/Gecko/SpiderMonkey, Servo, Ladybird), on the testing side (WPT, Test262), on specifications (W3C, WhatWG, TC39), on web compat (webcompat.com), or on documentation (MDN Web Docs, web.dev).

2026 Web Engines Hackfest

Web Platform community event for people working on the different engines (Chromium/Blink/V8, Safari/WebKit/JSC, Firefox/Gecko/SpiderMonkey, Servo, Ladybird), on the testing side (WPT, Test262), on specifications (W3C, WhatWG, TC39), on web compat (webcompat.com), or on documentation (MDN Web Docs, web.dev).

NLnet; Servo Webview for Tauri

The web ecosystem lacks a cross-platform, non-corporate controlled system for running web content. Tauri is a system for distributing cross-platform applications that relies on engines present on a system - effectively those owned by Apple, Google, and Microsoft. These permit varying levels of user control. The Servo project is a cross-platform, open source web engine.

sunil pai on Twitter / X

suspect we're a few months (if not weeks!) away from a model that's good enough for tool calling / small enough to be shipped on devices/OSes by default these already exist in research space, but hitting mainstream /consumer space is when it'll really take off. apps will be…— sunil pai (@threepointone) September 8, 2025

Servo Baseline Readiness

Servo is falling behind the web. It completes ~22 features/year at production quality, while the Baseline “Widely Available” set grows at ~52 features/year. At this pace, Servo plateaus around 80% by ~2037 and never catches up. Full velocity parity requires ~44 FTE (€8.8M/yr, €26.3M over 3yr). BWA features vary widely in real-world usage — a phased approach that prioritizes high-usage features first could reduce the initial headcount and cost by up to 40% while building toward full parity. The highest-leverage actions are unstalling 141 blocked features and fixing 51 regressions (features that lost >5 percentage points). This is a work-in-progress analysis focusing on one aspect of web engine development — feature-level readiness — and is not exhaustive. It is designed to orient thinking about cost and timelines. The central question: what would it cost in engineering investment alone to bring Servo to velocity parity within 3 years, excluding non-engineering and operational costs?

hdctools: Chrome OS Hardware Debug & Control Tools - Servo v4.1

"self embedding" Servo in a custom element · servo servo · Discussion #32883

Over in versotile-org/verso#79 there is some discussion about how to build a Servo based browser with a "chrome" UI written in HTML. The direction that the Verso team is exploring involve...

Browsers & Standards Work 2026: Call for Community Input

TL;DR: IPFS is planning the next phase of work to make browsers better for the decentralized web – not just IPFS, but any protocol that needs lightweight crypto, peer-to-peer connections, or native browser integration. We need your input on what features matters most. Background: What We’ve Accomplished Over the past 5 years, sustained collaboration with Igalia has delivered real improvements to all major browsers: Ed25519 in WebCrypto API - Shipped in Chrome 137 (May 2025), now available in...

🚨 AI News | TestingCatalog on Twitter / X

Perplexity Comet browser will get a native VPN support soon! ICYMI, it also got a native integration with 1Password recently, to help Comet agents to operate. https://t.co/7x4wpXqZqv pic.twitter.com/nzetLz8IQ7— 🚨 AI News | TestingCatalog (@testingcatalog) September 18, 2025

Digital Sovereignty in Practice: Web Browsers as a Reality Check

Servo, a memory-safe browser engine, is kept alive by five engineers and a trickle of donations. A reality check on what an independent browser would actually cost the digital-sovereignty talk.

Explosive MCP Adoption in 2 Years

Den Delimarsky, lead maintainer of the Model Context Protocol and Claude Code engineer at Anthropic, delivers a keynote on MCP's two-year journey from a basic protocol with two SDKs to the industry standard powering half a billion downloads per month. - **MCP's Origin Story** - Launched in November 2024 with a spec, two transports (STDIO and HTTP), two SDKs (Python and TypeScript), and a handful of clients including Claude Desktop - **Five Spec Releases** - Every revision was driven by community input, improving security, adding OAuth support, and simplifying the developer experience for building MCP clients and servers - **The March 2025 Inflection Point** - A 14-day window when major industry players publicly backed MCP, signaling enterprise adoption beyond the early enthusiast community - **MCP 2.0 Release** - The biggest spec update since launch, removing sessions for stateless deployment on AWS Lambda and Cloudflare Workers, and introducing the extensions framework - **Extensions Framework** - MCP Apps, Tasks, and Enterprise managed apps can now be tested as extensions before being added to the core specification - **Explosive Growth** - SDK downloads grew 13x year-over-year, reaching 500 million per month and 3.06 billion cumulative across Python, TypeScript, and C# alone - **Registry Scale** - The open-source MCP server registry surpassed 20,000 entries, a 45x increase since its September launch - **10 Official SDKs** - From the original two, MCP now supports Go (Google), C# (Microsoft), Kotlin (JetBrains), Swift, Rust, and more, each sponsored by major platform companies - **Community Momentum** - 184,000 GitHub stars, 2,500+ unique committers, 736 PRs merged and 600+ issues solved last month alone Whether you are building your first MCP server or scaling agent infrastructure across your organization, this keynote lays out exactly where the protocol stands and where it is heading. Links and Resources - MCP Specification: https://spec.modelcontextprotocol.io - MCP Blog: https://blog.modelcontextprotocol.io - MCP GitHub: https://github.com/modelcontextprotocol - Agentic AI Foundation: https://agenticaifoundation.org - Anthropic: https://www.anthropic.com Timestamps (approximate - adjust as needed) 00:00 Introduction 01:04 Two years of MCP: the origin story 02:43 MCP in 2024: the early days 03:40 Five spec releases in under two years 04:42 The 14 days that changed MCP adoption 05:39 MCP 2.0: the biggest release since launch 06:37 The extensions framework 07:04 MCP as enterprise agentic substrate 08:06 SDK download growth and registry scale 09:51 GitHub ecosystem metrics 11:04 From 2 SDKs to 10 11:55 Community momentum and contribution stats 12:16 Thank you to the MCP community #ModelContextProtocol #AgenticAI #MCPDevSummit