Skip to main content
Glama
extentos

extentos

by extentos

Extentos MCP Server

npm version license: MIT

Give your AI coding agent the tools to build smart-glasses apps.

Extentos is an MCP (Model Context Protocol) server that lets agents like Claude Code, Cursor, and Cline add smart-glasses capabilities — camera capture, voice triggers, live transcription, audio playback — to any Android or iOS app. The tools are deterministic: discovery, scaffolding, validation, and a browser-based simulator for end-to-end testing without hardware.

Works with Meta smart glasses today (Ray-Ban Meta, Oakley Meta, Meta Ray-Ban Display), with a multi-vendor architecture by design.

This repository is the public home of @extentos/mcp-server — releases, changelog, and issue tracking. The package ships on npm.

Install

Claude Code

claude mcp add extentos -- npx -y @extentos/mcp-server@latest

Cursor — one click:

Add to Cursor

Cline / any MCP client

{
  "mcpServers": {
    "extentos": {
      "command": "npx",
      "args": ["-y", "@extentos/mcp-server@latest"]
    }
  }
}

Requires Node 20+.

What your agent can do with it

Tool group

What it does

Discovery

getPlatformInfo, getCapabilityGuide, getCodeExample — the SDK capability catalog, per-feature call shapes in Kotlin + Swift, and canonical end-to-end patterns (voice Q&A, photo-describe, live transcription UI, …)

Scaffolding

generateConnectionModule — generates the connection UI + manifest + platform config for your app (Android or iOS)

Guidance

getVoiceCommandGuidance, getPermissions — implementation guidance the agent queries instead of guessing

Validation

inspectIntegration, validateIntegration — deterministic checks of the integration in your repo

Simulation

createSimulatorSession, getEventLog, getSimulatorStatus — a browser simulator running the same SDK code as production with only the transport swapped; the agent drives it and reads the event log to verify behavior

Production

getProductionChecklist, getCredentialGuide — the path from simulator to real glasses

Docs

searchDocs — bundled, versioned documentation topics

The workflow an agent typically runs: discover capabilities → scaffold the connection module → write handler code against the SDK → validate → simulate end-to-end → production checklist.

Tools

  • getPlatformInfo — SDK capability catalog, version/artifact info, and platform constraints

  • getCapabilityGuide — per-feature call shapes in Kotlin + Swift with gotchas

  • getCodeExample — canonical end-to-end patterns (voice Q&A, photo-describe, live transcription UI, …)

  • getMigrationGuide — mapping table and cutover plan from Meta DAT direct usage to Extentos

  • generateConnectionModule — scaffold the connection UI, manifest, and platform config into your app

  • getConnectionPageConfig — read the managed connection-page configuration

  • setConnectionPageConfig — update the managed connection-page configuration

  • regenerateConnectionPageFile — regenerate a managed connection-page file after config changes

  • adoptConnectionPageFile — bring an existing connection-page file under managed configuration

  • getAssistantConfig — read the managed voice-assistant configuration (model, voice, memory, wake sound)

  • setAssistantConfig — update the managed voice-assistant configuration

  • listProjectSounds — list custom sounds uploaded for the project

  • addProjectSound — upload a custom sound (earcons, wake sounds) to the project

  • shutter — trigger a camera shutter in the active simulator session

  • getGatewayUsage — AI-gateway usage and metering for the project

  • getCredentialStatus — which credentials (Meta DAT, AI provider) are configured

  • setCredential — store a credential for the project

  • getProjectAnalytics — usage analytics for the project's glasses integration

  • getVoiceCommandGuidance — implementation guidance for voice triggers and wake phrases

  • getPermissions — the exact permission set the integration needs per platform

  • inspectIntegration — read the current state of the integration in your repo

  • validateIntegration — deterministic checks of the integration (manifest, config, wiring)

  • createSimulatorSession — mint a browser-simulator session for end-to-end testing

  • ensureSimulatorBrowser — open/attach the simulator browser tab for the session

  • completeAuthLink — finish the device-code sign-in flow

  • getEventLog — read the session event log (transport, audio, camera, speak, toggle, stream, system)

  • injectTranscript — inject a voice transcript into the running app, as if the wearer spoke

  • injectAssistantUtterance — drive the voice assistant with an utterance end-to-end (real provider session)

  • assertToolCalled — wait for an assistant tool-call event matching name/args (agent E2E loop)

  • getSimulatorStatus — live session state: phase, roles, open streams, freshness, test videos

  • setSimVideo — pipe a test video into the simulated camera

  • setSimDevice — switch the simulated glasses model

  • getDisplayState — read the rendered display tree and interactive element ids (Ray-Ban Display)

  • injectInput — drive display input: select/navigate/back, like Neural Band gestures

  • injectHardwareButton — simulate the hardware capture button

  • getProductionChecklist — the path from simulator to real glasses

  • getCredentialGuide — how to obtain and configure Meta DAT credentials

  • searchDocs — search the bundled, versioned documentation topics

How it fits together

  • Your app depends on the native SDK: com.extentos:glasses (Android, Maven Central) or the Swift package (iOS)

  • Your code subscribes to capability primitives from its own handler classes — glasses.audio.transcriptions(), glasses.camera.capturePhoto(), glasses.audio.speak()

  • The simulator is the same app on a different substrate: WebSocket transport instead of Bluetooth, so agent-verified behavior carries to hardware

Discovery, validation, and guidance tools work anonymously. Creating browser-simulator sessions and scaffolding require a free account — the server walks the agent (and you) through a device-code sign-in when needed.

Issues & feedback

Bug reports and feedback are welcome — open an issue. The package is pre-1.0; tool surfaces may evolve between minor versions.

For security reports, see SECURITY.md — please don't open public issues for vulnerabilities.

License

MIT

Install Server
-
license - not tested
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
0dRelease cycle
2Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/extentos/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server