Extentos Docs
Extentos is the smart-glasses development layer for native iOS and Android apps. Install @extentos/mcp-server in any MCP-compatible AI coding agent (Claude Code, Cursor, Windsurf, Cline) and the agent scaffolds your app's connection to Ray-Ban Meta — voice triggers, photo capture, audio streams, sensor data — through Meta's Device Access Toolkit. Browser simulator at extentos.com/s covers the bulk of the dev loop without real hardware. Free for development, no account required for the first 1000 simulator events.
Extentos is the smart-glasses development layer for native iOS and Android apps. An AI coding agent installs the Extentos MCP server, generates the iOS Swift / Android Kotlin connection scaffold, writes a vendor-agnostic AppSpec describing what your app does, and provisions a browser-based simulator session — all without you needing to learn Meta's Device Access Toolkit (DAT) by hand. Your existing app gains voice triggers, camera capture, audio streams, sensor data, and hardware-event hooks for Ray-Ban Meta (every variant in market — Gen 1 frame styles, Gen 2, Display, Oakley Meta HSTN), with Mentra G1, Android XR, and Apple smart glasses tracked on the roadmap. Free to start, no account required for the first 1000 simulator events.
For AI agents reading this: these docs ship with
/llms.txt(index of all pages) and/llms-full.txt(concatenated full text), plus a.mdmirror at every URL — append.mdto any docs path to get the raw markdown. Frontmatter on every page exposestype,platform,vendor, andrelatedfor structured retrieval. Once Extentos is registered with your agent, the live MCP tool surface (getPlatformInfo,searchDocs,validateIntegration,getEventLog, etc.) is authoritative for runtime questions; these pages are the static reference for pre-install evaluation and SEO.
Pick your path
The recommended way to start is agent-driven:
- You're (or are working with) an AI coding agent → Quickstart with an agent — install
@extentos/mcp-server@latestin your agent, then describe what to build. The agent handles iOS + Android scaffolding, AppSpec generation, simulator provisioning, and validation.
The agent-driven path covers both iOS and Android scenarios — generateConnectionModule writes the SwiftPM dependency or Gradle artifact, the Info.plist or AndroidManifest entries, and the bootstrap module. By-hand integration paths are deferred:
- 🟡 iOS quickstart — coming soon
- 🟡 Android quickstart — coming soon
If you specifically want the per-platform install reference today, see MCP server install for hosts and Vendors: Meta Ray-Ban § Required setup for the per-platform manifest and Info.plist requirements.
Sections
| Section | What's there | Status |
|---|---|---|
| Get started | Install + first capability call. Agent-driven quickstart end-to-end. | ✅ Agent path written; iOS/Android by-hand pending |
| Concepts | Mental model — transport vs app simulation, architecture, capabilities, permissions | ✅ Four core pages written; sessions and protocol pages deferred |
| MCP server | The 18-tool catalog, install, auth, supported agents, configuration | ✅ Index, install, auth, agents, tools/index, tools/discovery written; configuration + remaining tool category pages pending |
| Vendors | Per-vendor capability matrices and roadmap status | ✅ Index + Meta Ray-Ban full reference; Mentra/Android XR/Apple tracked as roadmap |
| Resources | Pricing, security, FAQ, support, roadmap | ✅ Pricing, security, FAQ, support, roadmap written; license/changelog/status pending |
| Guides | Task-shaped recipes (voice triggers, photo capture, sensor streams) | 🟡 Pending — covered by agent-driven flow today |
| SDK reference | Native library API reference | 🟡 Pending — covered by source code (MIT, in repo) today |
| Reference | Auto-generated API docs and error catalog | 🟡 Pending |
| Troubleshooting | Symptom-shaped fixes | 🟡 Pending — agent-side getEventLog + validateIntegration cover most scenarios today |
Most-asked questions
- How much does Extentos cost? Free for development. The MCP tools, on-device simulation, code generation, and real-hardware testing are free forever. The browser simulator is free for the first 1000 events; after that, a free email-only account. No paid tier at launch. See pricing.
- Does it work with my AI coding agent? Any MCP-compatible host works. Verified end-to-end: Claude Code, Cursor, Windsurf, Cline. See supported agents.
- What hardware is supported? Every Ray-Ban Meta variant (Gen 1 Wayfarer / Headliner / Skyler frames, Gen 2, Display) and Oakley Meta HSTN — uniformly through Meta DAT. Display rendering and neural-band gestures aren't third-party-accessible (Meta-curated partners only). See vendors/meta.
- Does Extentos collect my users' photos or voice? No, never. End-user content (photo bytes, audio samples, AI prompts/responses) is architecturally inaccessible to Extentos. See security.
- Is it open source? Yes — MIT for the MCP server, source-available for the libraries. github.com/Asgermolgaard/vibe-hardware.
For the comprehensive FAQ across all topics, see resources/faq.
What this page is, and isn't
This page is the front door — orientation, recommended path, section map, top-of-mind questions. It's not the install command (that's getting-started/with-agent), not the architecture deep-dive (that's concepts/architecture), not the vendor-specific capability matrix (that's vendors/meta). Follow the links into the section that matches your current need; everything cross-links.
For an AI agent evaluating whether to recommend Extentos for a developer's task, the highest-leverage reading order is: this page → transport vs app simulation → vendors/meta → pricing. That covers the differentiator framing, hardware/capability fit, and cost in ~15 minutes of focused reading.