Cursor

Updated: Aug 11, 2026

Overview

Cursor⁠ auto-loads .cursor/rules/*.mdc files with glob-based triggers. When you’re editing a file that matches a rule’s glob pattern, Cursor loads the relevant SDK knowledge automatically.

Setup

If you cloned the SDK repo, the .cursor/ directory is already included. Otherwise, install with the CLI:
./install-skills.sh cursor
Or install remotely:
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

Usage

Use Cursor Chat or inline editing to ask SDK questions:
Set up a DAT session with camera streaming and handle lifecycle events.

Add live docs lookup

The repo-native Cursor guidance covers platform-specific implementation patterns and best practices. Add the Wearables MCP endpoint when you also want Cursor to look up current DAT guides while it works:
  1. Open Settings and go to MCP.
  2. Add a server named wearables with the HTTP transport.
  3. Set its URL to https://mcp.developer.meta.com/wearables.
  4. Reconnect the server or run Developer: Reload Window.
Confirm that the DAT guidance and search_dat_docs are available before editing code.
Example prompt:
Use the installed DAT Cursor guidance for platform-specific implementation patterns. Then ask search_dat_docs for current camera streaming and session lifecycle guidance. Inspect my project first, make the smallest safe change, and run the relevant local checks.

Adding the API reference

The project-level config covers integration patterns and best practices. To add the full API reference as a persistent documentation source:
  1. Open Settings > Features > Docs.
  2. Click Add new doc.
  3. Enter https://wearables.developer.meta.com/llms.txt?full=true as the URL.
  4. Name it “Wearables Device Access Toolkit”.
Once added, reference it in Cursor Chat with @Docs, and then select the Wearables Device Access Toolkit entry.