DAT MCP

Updated: Jun 2, 2026

Overview

The Wearables Device Access Toolkit uses the shared public Wearables MCP server for live DAT documentation search. Use it when you want your editor or agent to query current guides and API reference instead of relying only on repo-local config files.
The server exposes a DAT-specific tool:
  • search_dat_docs — semantic search over DAT guides, API reference, and code examples
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 the repo config for coding patterns and setup guidance, and use the MCP endpoint for live DAT docs lookup.

Claude Code

Add the DAT 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
Example prompt:
Search the Wearables DAT docs for camera streaming setup on Android.

Cursor

Add the endpoint as an HTTP MCP server:
  1. Open Settings and go to MCP.
  2. Add a new server.
  3. Set the name to wearables.
  4. Set the transport or server type to HTTP.
  5. 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. You can 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:
  1. Set Transport Type to Streamable HTTP.
  2. Set URL to https://mcp.developer.meta.com/wearables.
  3. Set Connection Type to Direct.
  4. Click Connect.
Run:
  1. Initialize the session.
  2. Open Tools and click List Tools.
  3. Confirm that search_dat_docs is present.
  4. Run search_dat_docs with a query such as camera streaming.
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:
  • How do I stream camera on Ray-Ban Meta glasses? Returns the camera streaming guide, including Session.addStream(...), 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

SymptomLikely causeFix
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