DAT MCP

Updated: Aug 11, 2026

Overview

The recommended AI-assisted setup for the Wearables Device Access Toolkit combines the DAT GitHub plugin or repo-native skills for your platform with the shared public Wearables MCP server. Choose iOS or Android first. The plugin or skills provide platform-specific implementation and testing workflows; MCP provides current documentation lookup while the assistant works.

The server exposes a DAT-specific tool:

search_dat_docs — semantic search over DAT guides, API reference, and code examples

When your client exposes an output or response format option, choose Markdown. Markdown results preserve headings, links, tables, and code blocks, which makes it easier for the assistant to quote the docs accurately before editing code.

The public endpoint is:

https://mcp.developer.meta.com/wearables

Use the direct MCP host above. Do not use the Wearables developer site URL as the MCP endpoint.

This server complements the project-level AI config described in the AI-Assisted Development overview. Use llms.txt⁠ as a supplementary source when you need exact API reference details.

Use this page with AI

Copy this prompt into your AI tool to configure both parts of the recommended setup:

Use https://wearables.developer.meta.com/docs/develop/dat/ai-assisted-mcp/ to configure AI-assisted DAT development. Inspect this project and identify whether it targets iOS or Android. If the matching DAT GitHub plugin or repo-native skills are missing, install them using the instructions for my platform and AI tool. Add the Wearables MCP endpoint https://mcp.developer.meta.com/wearables, verify that the DAT coding guidance and search_dat_docs are available, and ask search_dat_docs what I should install and check before building my first DAT app. Do not edit app code until both tools are ready and the test query returns relevant guidance.

Claude Code

Add the DAT repository for your platform as a Claude Code plugin marketplace, then install its plugin.

iOS:

claude plugin marketplace add facebook/meta-wearables-dat-ios
claude plugin install mwdat-ios@mwdat-ios-marketplace

Android:

claude plugin marketplace add facebook/meta-wearables-dat-android
claude plugin install mwdat-android@mwdat-android-marketplace

Then add the Wearables MCP server with the Claude CLI:

claude mcp add --transport http wearables https://mcp.developer.meta.com/wearables

To check the configuration into your project, use project scope:

claude mcp add --transport http wearables --scope project https://mcp.developer.meta.com/wearables

Verify that Claude Code can see the server:

claude mcp list

Start a fresh Claude Code session if the running session does not discover the plugin or MCP server. Confirm that the platform plugin and search_dat_docs are available.

Example prompt:

Use the installed DAT plugin for platform-specific implementation guidance. Then ask search_dat_docs what I should install and check before building my first DAT app.

Codex

Add the DAT repository for your platform as a Codex plugin marketplace, then install its plugin.

iOS:

codex plugin marketplace add facebook/meta-wearables-dat-ios
codex plugin add mwdat-ios@mwdat-ios-marketplace

Android:

codex plugin marketplace add facebook/meta-wearables-dat-android
codex plugin add mwdat-android@mwdat-android-marketplace

Then add the Wearables MCP server with the Codex CLI:

codex mcp add wearables --url https://mcp.developer.meta.com/wearables

Verify that the server is enabled:

codex mcp list

Start a fresh Codex session if the running session does not discover the plugin or MCP server. Confirm that the platform plugin and search_dat_docs are available.

Example prompt:

Use the installed DAT plugin for platform-specific implementation guidance. Then ask search_dat_docs what I should install and check before building my first DAT app.

Cursor

Install the repo-native Cursor guidance for your platform.

iOS:

curl -sL https://raw.githubusercontent.com/facebook/meta-wearables-dat-ios/main/install-skills.sh | bash -s cursor

Android:

curl -sL https://raw.githubusercontent.com/facebook/meta-wearables-dat-android/main/install-skills.sh | bash -s cursor

Restart Cursor or run Developer: Reload Window so it discovers the DAT guidance. Then add the endpoint as an HTTP MCP server:

Open Settings and go to MCP.

Add a new server.

Set the name to wearables.

Set the transport or server type to HTTP.

Use https://mcp.developer.meta.com/wearables as the URL.

If your Cursor build uses JSON-backed MCP settings, the entry should look like this:

{
  "mcpServers": {
    "wearables": {
      "type": "http",
      "url": "https://mcp.developer.meta.com/wearables"
    }
  }
}

After saving the config, reconnect the server or restart Cursor. Confirm that the DAT guidance and search_dat_docs are available, then ask Cursor Chat to search the DAT docs through the MCP tool.

MCP Inspector

Use MCP Inspector for a direct endpoint check:

npx @modelcontextprotocol/inspector

In the browser UI:

Set Transport Type to Streamable HTTP.

Set URL to https://mcp.developer.meta.com/wearables.

Set Connection Type to Direct.

Click Connect.

Run:

Initialize the session.

Open Tools and click List Tools.

Confirm that search_dat_docs is present.

Run search_dat_docs with a query such as camera streaming, and request Markdown output if your client exposes a format option.

If your Inspector build labels the transport as HTTP instead of Streamable HTTP, use the HTTP option with the same URL.

Example queries

These are representative queries we tested against the DAT MCP:

I want to build my first DAT app with an AI coding assistant. What should I install and check before I start? Returns platform plugin or skills guidance, MCP setup, environment requirements, and relevant first-project documentation.

How do I stream camera on Ray-Ban Meta glasses? Returns the camera streaming guide, including Session.addCamera(...), StreamConfiguration, valid frame rates, quality levels, and device-side caveats such as hinge-close and doff behavior.

How do I initialize the DAT SDK? Returns SDK startup and device session details such as Wearables.initialize(context), WearablesError.NOT_INITIALIZED, SessionState, and the platform-specific session state listeners.

How do I test DAT integrations without physical glasses? Returns Mock Device Kit guidance, including the Mock Device Kit docs, simulated media streaming, and the Android and iOS MDK testing guides.

Bluetooth connection lifecycle events Returns SessionState transition behavior, device availability callbacks such as devicesMetadata on Android and addLinkStateListener on iOS, and the fact that reopening the hinges restores Bluetooth but does not restart the session.

Troubleshooting

Symptom	Likely cause	Fix
The server does not connect	The client is still using the old DAT-specific URL or cached config	Re-enter `https://mcp.developer.meta.com/wearables` and reconnect
No tools appear	The client did not finish initialization	Reconnect, then run initialize before `tools/list`
The client asks for auth	The server was configured with stale custom headers	Remove custom auth headers and reconnect
Search results are too broad	The query is too vague	Include the platform, module, or exact API name in the query