License
Extentos license terms. The @extentos/mcp-server npm package is MIT-licensed (declared in its package.json, surfaced on the npm package page). The Android library (com.extentos:glasses) and the iOS library (Extentos) are distributed as public packages with proprietary source. This page states the current, verifiable licensing position per component.
This page states the current, verifiable licensing position for each Extentos component. Extentos is pre-1.0; where a component's formal license terms aren't yet finalized, this page says so plainly rather than implying more than is committed.
MCP server — MIT
The @extentos/mcp-server npm package is MIT-licensed. This is declared in the package's package.json ("license": "MIT") and is shown on the npm package page. MIT permits commercial use, modification, distribution, and private use, with the standard attribution and no-warranty terms.
This covers the MCP tooling you run via npx -y @extentos/mcp-server@latest — discovery, code generation, validation, and simulator orchestration. The code it generates into your app is yours to license however you choose; the generator is MIT.
Native libraries — public packages, proprietary source
The Android library (com.extentos:glasses + com.extentos:glasses-ui, package com.extentos.glasses.core) ships as a public artifact on Maven Central; the iOS library (Extentos) ships as a Swift package from swift-glasses on GitHub. You depend on the published packages and build against their public API — the library source is proprietary and not distributed.
There is no open-source grant for the libraries today, and no separate LICENSE file. If you need a specific license commitment — commercial use, redistribution — email hello@extentos.com and ask.
License position by component
| Component | Distribution | License position |
|---|---|---|
@extentos/mcp-server | npm | MIT (declared in package.json) |
Android library (com.extentos:glasses, :glasses-ui) | Maven Central (binary) | Proprietary; no open-source grant |
iOS library (Extentos) | Swift package (swift-glasses on GitHub) | Proprietary; no open-source grant |
| Web app, backend, docs | Not distributed | Proprietary |
Third-party dependencies
Extentos builds on third-party SDKs and libraries that carry their own licenses — most notably Meta's Device Access Toolkit (governed by Meta's developer terms, not Extentos's license) and the usual npm / Gradle / SPM dependency trees. Your obligations toward those are independent of Extentos's MIT grant on the MCP server. In particular, shipping to real Meta Ray-Ban hardware requires accepting Meta's developer terms via your own Meta Developer Center registration.
Questions
If you need a clarification on licensing — commercial use, redistribution of the libraries, or a written license commitment ahead of the pending LICENSE file — email hello@extentos.com with the [license] prefix. The maintainer treats licensing questions as high priority because they block downstream adoption.
Related
- Changelog — release history per component
- Support — how to file issues, including licensing questions
- Install — getting the MIT-licensed MCP server running
Related
Changelog
Release notes for Extentos — the MCP server (@extentos/mcp-server), the Android library (com.extentos:glasses), and the iOS library (swift-glasses). Newest first. The MCP server is pre-1.0; APIs may shift between minor versions until the hardware test loop closes. The first stable iOS release (the 1.7.0 lockstep cut), the managed AI gateway, the Phase-4 voice assistant, and the display capability are the most recent additions; the pure-SDK pivot, the browser simulator, getEventLog, auto-bind, and device-code auth landed earlier.
Support
How to get help with Extentos — self-service diagnostics through the extentos-mcp CLI (whoami, status, getEventLog), what to include when you email support so it's actionable across the four components (MCP server, native libraries, backend, simulator UI), the security disclosure path, and pre-1.0 response expectations. No paid support tiers exist at launch.
Install the MCP server
How to install the Extentos MCP server (@extentos/mcp-server) in any MCP-compatible AI coding agent — Claude Code, Cursor, Windsurf, Cline, and others. Per-host install commands, config file locations, copy-pasteable JSON snippets, restart and verify steps, version pinning, updating, troubleshooting common errors, and uninstall instructions. Verified install paths for each supported host.
Status
Service status for Extentos. There is no public status page or uptime instrumentation yet — Extentos is pre-1.0. The backend that powers the browser simulator and the managed AI gateway runs at api.extentos.com. For what shipped, see the changelog; to report an outage or incident, email hello@extentos.com with the [incident] prefix.
Roadmap
The Extentos public roadmap — shipping today (Meta Ray-Ban, both native SDKs, managed AI gateway, the voice assistant, display), in development, and tracked further out.