---
title: License
description: 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.
type: resource
platform: all
related:
  - /docs/resources/changelog
  - /docs/resources/support
  - /docs/mcp-server/install
---

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](https://www.npmjs.com/package/@extentos/mcp-server). 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](https://central.sonatype.com/artifact/com.extentos/glasses); the **iOS library** (`Extentos`) ships as a Swift package from [swift-glasses on GitHub](https://github.com/extentos/swift-glasses). 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](mailto:hello@extentos.com) and ask.

## License position by component

| Component | Distribution | License position |
|---|---|---|
| `@extentos/mcp-server` | [npm](https://www.npmjs.com/package/@extentos/mcp-server) | **MIT** (declared in `package.json`) |
| Android library (`com.extentos:glasses`, `:glasses-ui`) | [Maven Central](https://central.sonatype.com/artifact/com.extentos/glasses) (binary) | Proprietary; no open-source grant |
| iOS library (`Extentos`) | Swift package ([swift-glasses on GitHub](https://github.com/extentos/swift-glasses)) | 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](https://developers.meta.com) 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](mailto:hello@extentos.com) with the `[license]` prefix. The maintainer treats licensing questions as high priority because they block downstream adoption.

## Related

- **[Changelog](/docs/resources/changelog)** — release history per component
- **[Support](/docs/resources/support)** — how to file issues, including licensing questions
- **[Install](/docs/mcp-server/install)** — getting the MIT-licensed MCP server running