---
title: Extentos Docs
description: The AI smart-glasses development studio for Meta Ray-Ban — MCP server, Kotlin/Swift SDK, and browser simulator docs. Free to start, no hardware required.
type: overview
platform: all
related:
  - /docs/getting-started/with-agent
  - /docs/concepts/transport-vs-app
  - /docs/vendors/meta
  - /docs/mcp-server
  - /docs/resources/pricing
  - /docs/resources/security
---

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, and provisions a browser-based simulator session — all without you needing to learn Meta's Wearables Device Access Toolkit (DAT) by hand. Your app code subscribes to typed SDK primitives (`glasses.audio.transcriptions()`, `glasses.camera.capturePhoto()`, `glasses.audio.speak()`, …) from your own handler classes; the library wraps multi-vendor transport so the same code runs against the simulator, Meta Ray-Ban, and future supported devices. **Meta smart glasses** (every variant in market — Gen 1 frame styles, Gen 2, Ray-Ban Meta Optics, Oakley Meta HSTN, Oakley Meta Vanguard, Meta Glasses, and Ray-Ban Meta Display) are supported in production today. **[Android XR](/docs/vendors/android-xr)** is in preview — the projected transport is built and proven on Google's emulator, and the simulator carries an Android XR device identity, though the module is unpublished and no hardware is buyable yet. Apple smart glasses are tracked. Free to start. Discovery, validation, on-device simulation, and real-hardware testing work without an account; the scaffold step and the browser simulator at extentos.com/s link a free email-only account.

## 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](/docs/getting-started/with-agent) — install `@extentos/mcp-server@latest` in your agent, then describe what to build. The agent handles iOS + Android scaffolding, handler-code composition (peeling from `getCodeExample`'s canonical Kotlin/Swift patterns), 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. The by-hand integration paths:

- ✅ [iOS quickstart](/docs/getting-started/ios) — the by-hand SwiftPM path
- ✅ [Android quickstart](/docs/getting-started/android) — the by-hand Gradle path

If you specifically want the per-platform install reference today, see [MCP server install](/docs/mcp-server/install) for hosts and [Vendors: Meta Ray-Ban § Required setup](/docs/vendors/meta#required-setup-for-development) for the per-platform manifest and Info.plist requirements.

## Sections

| Section | What's there | Status |
|---|---|---|
| **[Get started](/docs/getting-started)** | Install + first capability call. Agent-driven quickstart end-to-end. | ✅ Agent path complete; Android + iOS by-hand quickstarts published |
| **[Concepts](/docs/concepts)** | Mental model — transport vs app simulation, architecture, capabilities, the AI gateway, the assistant runtime, display, sessions, permissions, projects | ✅ Written |
| **[Guides](/docs/guides)** | Task-shaped recipes — voice triggers, the voice assistant, photo/video/audio capture, display, hardware events, disconnects, sim→hardware | ✅ Written |
| **[MCP server](/docs/mcp-server)** | The tool catalog, install, auth, supported agents, per-category tool pages | ✅ Written |
| **[SDK reference](/docs/sdk)** | Native library API reference | ✅ Android + iOS written |
| **[Vendors](/docs/vendors)** | Per-vendor capability matrices and support status | ✅ Index + Meta full build guide; [Android XR](/docs/vendors/android-xr) and [Brilliant Labs](/docs/vendors/brilliant) preview status; Apple tracked |
| **[Reference](/docs/reference)** | Generated MCP-tool + error catalogs, API reference | ✅ MCP tools + errors generated from source; hand-maintained Android/iOS API pages |
| **[Troubleshooting](/docs/troubleshooting)** | Symptom-shaped fixes | ✅ Core symptoms written; agent-side `getEventLog` + `validateIntegration` cover the rest |
| **[Resources](/docs/resources)** | Pricing, security, FAQ, support, roadmap, changelog, license, status | ✅ Written |

## Most-asked questions

- **How much does Extentos cost?** Most of it is free with no account — discovery, validation, and guidance MCP tools, on-device simulation, and real-hardware testing. Two surfaces link a free email-only account (no card): the browser simulator and the `generateConnectionModule` scaffold step. The one metered surface is the [managed AI gateway](/docs/concepts/ai-gateway) behind the voice assistant: billing is live on a prepaid-credit model — every account starts with $2 of free credit. See [pricing](/docs/resources/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](/docs/mcp-server/agents).
- **What hardware is supported?** Every Ray-Ban Meta and Oakley Meta variant (Gen 1 / Gen 2 frames, Ray-Ban Meta Optics, Oakley Meta HSTN and Vanguard) plus Ray-Ban Display — uniformly through Meta DAT. Third-party **display rendering is supported** via `glasses.display.*` in both SDKs (on-glasses rendering via Meta DAT is live on Android; iOS on-glasses delivery is in progress); what stays Meta-only is the full-screen first-party system surface (Meta's own navigation, WhatsApp, captions) and raw neural-band gestures. See [vendors/meta](/docs/vendors/meta).
- **Does Extentos collect my users' photos or voice?** No. Photo bytes and audio samples are architecturally inaccessible to Extentos. The default managed AI gateway relays the voice assistant's audio and text to the model provider but never stores it; bring-your-own-key calls from your own handler code never touch Extentos at all. See [security](/docs/resources/security).
- **Is it open source?** The MCP server (`@extentos/mcp-server`) is MIT-licensed on [npm](https://www.npmjs.com/package/@extentos/mcp-server). The Android SDK is a public package on [Maven Central](https://central.sonatype.com/artifact/com.extentos/glasses) and the iOS SDK is a public Swift package on [GitHub](https://github.com/extentos/swift-glasses) that you build against; the libraries' source is proprietary, as is the wider platform (backend, dashboard).

For the comprehensive FAQ across all topics, see [resources/faq](/docs/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](/docs/getting-started/with-agent)), not the architecture deep-dive (that's [concepts/architecture](/docs/concepts/architecture)), not the vendor-specific capability matrix (that's [vendors/meta](/docs/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](/docs/concepts/transport-vs-app) → [vendors/meta](/docs/vendors/meta) → [pricing](/docs/resources/pricing). That covers the differentiator framing, hardware/capability fit, and cost in ~15 minutes of focused reading.