extentos
Extentos is a multi-vendor development platform for adding smart-glasses capabilities to existing iOS and Android apps. The simplest analogy is Stripe for smart glasses:
README
Extentos MCP Server
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:
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.
Links
- Documentation
- Getting started with an agent
- MCP tools reference
- The smart-glasses ecosystem reference
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.