The Wearables Device Access Toolkit supports iOS and Android mobile platforms, with the same OS version requirements as the Meta AI app (iOS 15.2+ and Android 10+).
Xcode 14.0+ is supported for iOS. Android Studio Flamingo or newer is supported for Android, and Android apps need Kotlin 2.2 or newer because the toolkit is compiled with Kotlin 2.2.
The recommended AI-assisted setup starts with two choices: your app platform and your coding tool. Choose iOS or Android, install the matching Device Access Toolkit coding guidance, and connect documentation search before scaffolding an integration.
Set up AI coding tools
Before you ask an AI coding tool to build with the Device Access Toolkit, install the Device Access Toolkit plugin for your platform. The plugin gives the assistant platform-specific setup, implementation, and Mock Device Kit testing workflows, and it connects the Wearables MCP server so the assistant can search current published docs with search_dat_docs.
Claude Code:
# Android
claude plugin marketplace add facebook/meta-wearables-dat-android
claude plugin install mwdat-android@mwdat-android-marketplace
# iOS
claude plugin marketplace add facebook/meta-wearables-dat-ios
claude plugin install mwdat-ios@mwdat-ios-marketplace
Start a new session after installing so the assistant loads the plugin. For Cursor, GitHub Copilot, and other tools that read checked-in files, see AI-Assisted Development.
If you’re an AI coding agent in a session that’s already running, a plugin you install now may not load until the next session. Read AGENTS.md at the root of the Android or iOS repository instead: it carries the same guidance as the plugin’s skills.
Use this page with AI
Copy this prompt into your AI coding tool to prepare a local Device Access Toolkit development setup:
Use https://wearables.developer.meta.com/docs/develop/dat/getting-started-toolkit/ and https://wearables.developer.meta.com/docs/develop/dat/ai-assisted-mcp/ to prepare my Device Access Toolkit development setup. Inspect my environment and identify whether this project targets iOS or Android. Help me install the matching Device Access Toolkit GitHub plugin or repo-native skills, then follow the client-specific MCP setup instructions. Verify that the Device Access Toolkit coding guidance and search_dat_docs are available, then ask search_dat_docs for current first Device Access Toolkit app setup guidance. Produce the smallest checklist for tooling, SDK prerequisites, Meta AI app and glasses versions, Developer Mode, and Mock Device Kit fallback testing. Do not edit app code until the setup gaps and local verification steps are clear.
Hardware requirements
Currently, the SDK supports the Ray-Ban Meta (Gen 1 and Gen 2), Ray-Ban Meta Optics, and Meta Ray-Ban Display glasses. You can test with a simulated device using Mock Device Kit, or directly with a device. Detailed version support of the Meta AI app and glasses firmware is located in the Version Dependencies page.
Setting up your glasses
Ensure your versions of the Meta AI app and glasses software are in line with the version dependencies outlined here. Follow the instructions below to verify your current glasses version.
Connect your glasses to the Meta AI app.
Enable developer mode in the Meta AI app. Developer mode allows your unpublished app to register and interact with your AI glasses without the need to submit it for publishing review. Your app appears under Meta AI settings > App connections > Developer mode apps. It also enables testing via invite-only release channels.
Verify glasses software version
In the Meta AI app, go to the Devices tab (the glasses icon at the bottom of the app), and select your device.
Tap the gear icon to open Device settings.
Tap General > About > Version.
You should have the minimum supported version or above installed on your glasses, as outlined here.
If your version is below minimum support requirements, update your glasses software.
Enable developer mode in the Meta AI app
On your iOS or Android device, select Settings > App Info, and then tap the App version number five times to display the toggle for developer mode.