Meta's Ray-Ban Display toolkit adds voice control for web apps, off by default
Meta has published developer instructions for making Ray-Ban Display web apps answerable to Meta AI, so that a wearer can operate an app by speaking to the assistant rather than clicking through it. The 291-line instruction file landed on October 1 at 20:52 UTC in a commit to facebook/meta-wearables-webapp, and it states plainly that the capability is "off by default and enabled per device, by Developer Mode or by rollout".

On stage at Meta Connect 2026. Image: Meta
The mechanism is a browser interface called WebMCP. Developers register tools on document.modelContext, which Meta says the browser installs before page scripts run, and Meta's instructions sum up the result in one line: "The wearer speaks to Meta AI, Meta AI calls your tools, the app updates. No SDK, no speech recognition, no wake word: the browser provides the surface."
This is a toolkit update rather than a feature anyone can switch on. The repository, which Meta calls an "AI-assisted development toolkit for building web applications on Meta Ray-Ban Display glasses", adds that eligibility "is decided once when the app launches and does not change for the rest of that session", so turning WebMCP on mid-session does nothing until the app is relaunched.
Meta says the D-pad has to keep working
The instruction to developers is blunt: "This is additive. The app must stay fully usable by D-pad with no assistant at all." Meta also tells them to test the app driven by D-pad only, and again on a build where the voice surface is absent.
Voice is being treated as a layer over an app that has to work without it, which is what you would expect of a capability that reaches devices by rollout rather than by a store update.
Meta ships the toolkit as plugins for four AI coding tools, Muse Code, Claude Code, Codex and Cursor, and the commit bumps those manifests to version 128.1.0. The repository was created on May 8 and carried 206 stars when we read it on October 2 at 21:20 UTC.
The parameter rules are strict, and they fail quietly
Most of Meta's guidance is about what breaks. Tool parameters are carried only as a boolean, an integer, a number or a string: "There is no array or object parameter type", and declaring one anyway carries the value as a JSON-encoded string that "fails outright when what arrives is not valid JSON of the declared kind".
Schema constraints are worth less than they look. Meta writes that "enum", "items", "minimum", "maximum", "default" and nested schemas "are dropped and never enforced", so developers are told to put those limits in the description instead and validate the arguments inside the tool itself, which Meta says gets "a 10-second deadline for assistant-originated calls".
There is also no way for a tool to report that it failed. "A fulfilled result is always reported as success, and isError is dropped", Meta says, so an app has to answer an unsuccessful request with an ordinary result whose contents describe the problem. Tool names accept 128 characters, but Meta AI re-registers each one inside a 64-character budget, leaving 57, and Meta warns that two names agreeing that far collide with no error, "with the tool simply never reaching Meta AI".
The rollout has no date and the docs page is gated
Meta has not said when WebMCP reaches wearers. The matching developer documentation page is not public either: Meta's commit message says it is "still gated, so it is not linked from here", with an instruction to add the link "when the gate lifts". Nothing in the repository says which apps will get WebMCP, how many wearers are in the rollout, or when it widens.
For buyers, the glasses themselves are further along than the toolkit. Meta Ray-Ban Display goes on sale in the UK at £749, with Germany at €899 on October 13, and Meta has been building voice into its own features on the glasses, including hologram calls on WhatsApp driven by your voice rather than your face. Third-party apps answering the same assistant are, for now, a set of rules on GitHub and a capability Meta says is "off by default".