Enable AI tools with MCP for Meta Horizon OS developers

• Your editor (VS Code, Cursor, or Antigravity) — install the Meta Horizon extension.
• Meta Quest Developer Hub (MQDH) — a standalone desktop app with a guided setup UI.
• The agentic-tools plugin (Claude Code, Cursor, GitHub Copilot, and more) — installs the hzdb MCP server and agentic skills in one step.
• Node.js (npx) — manual setup that works with any MCP-compatible agent.

• Android Studio
• Augment Code
• Claude Code
• Claude Desktop
• Cline
• Cursor
• Gemini CLI
• JetBrains AI Assistant
• OpenAI Codex
• Roo Code
• Zed

1. Go to Settings > AI tools.
2. Click Add to VS Code.

claude plugin marketplace add meta-quest/agentic-tools
claude plugin install agentic-tools@meta-quest

npx skills add meta-quest/agentic-tools

• Node.js⁠ v18 or later
• npm (included with Node.js)
• [Optional] ADB⁠. hzdb includes a built-in device communication library, so ADB is not required. Install ADB separately if you experience device connectivity issues.

npx @meta-quest/hzdb

npx @meta-quest/hzdb --version

1. In your project root, create the file .vscode/mcp.json (or open it if it already exists).
2. Paste the following configuration:

    {
      "servers": {
        "meta-horizon-mcp": {
          "command": "npx",
          "args": ["-y", "@meta-quest/hzdb", "mcp", "server"]
        }
      }
    }
   
3. Restart VS Code or reload the window (Cmd+Shift+P > Developer: Reload Window) so VS Code picks up the new MCP server.

npx -y @meta-quest/hzdb mcp server

{
  "mcpServers": {
    "meta-horizon-mcp": {
      "command": "npx",
      "args": ["-y", "@meta-quest/hzdb", "mcp", "server"]
    }
  }
}

npx -y @meta-quest/hzdb mcp server

# Search documentation
npx @meta-quest/hzdb search-doc "passthrough rendering"

# Pull device logs
npx @meta-quest/hzdb logcat --lines 100 --level error

# Capture a screenshot from a connected Quest
npx @meta-quest/hzdb screenshot

# Search Meta's 3D asset library
npx @meta-quest/hzdb asset-search "realistic indoor furniture"

1. Browse documentation — “Search the documentation for passthrough rendering.” You should receive a list of relevant documentation pages.
2. Fetch a specific page — Pick a page from the results and ask: “Fetch the documentation at [URL].” You should see the full page content returned.
3. Search 3D assets — “Find 5 realistic indoor furniture models.” The MCP server returns download URLs and preview images from Meta’s asset library.

1. Pull device logs — “Get 50 lines of logcat filtered to error level.” This confirms ADB and device communication are working.
2. Capture a screenshot — “Take a screenshot from my connected Quest device.”

1. Call get_perfetto_context to initialize the performance analysis context.
2. Call load_trace_for_analysis with the session_id (the trace file name) to load a captured trace.
3. Use trace_thread_state, run_sql_query, or get_counter_for_gpu_frames to query the loaded trace.

• Check that VS Code is installed. The button opens a vscode:// URI link. If VS Code is not installed, your system won’t have a handler for this URI and nothing will happen. Install VS Code⁠ first, then try again.
• Check if VS Code opened in the background. VS Code may launch but not appear on top of other windows. Check your taskbar or dock for the VS Code icon after clicking the button.
• Try installing the extension manually. Open VS Code, go to Extensions (Cmd+Shift+X on Mac, Ctrl+Shift+X on Windows), and search for Meta Horizon, or install it directly from the VS Code Marketplace⁠. If the extension is not listed, use Option D: Install through Node.js (npx) instead.

• Check your Node.js version. The MCP server requires Node.js v18 or later. Run node --version to verify.
• Check for npm errors. If you see npm error 404 Not Found when running npx -y @meta-quest/hzdb mcp server, the package may not be available yet. Check the @meta-quest/hzdb npm page⁠ to confirm it is published.
• Validate your JSON configuration. A missing comma or extra bracket in your agent’s MCP config file will prevent the server from starting. Paste your config into a JSON validator if you’re unsure.
• Check the command path. Make sure npx is available on your system PATH. Run npx --version to confirm.

• Check that the plugin is installed. Verify the agentic-tools plugin is installed and enabled in your agent. For Claude Code, run claude plugin list and confirm agentic-tools@meta-quest appears with status enabled. For other agents, consult the repository README⁠ for verification steps.
• Restart your AI agent. After installing or updating plugins, restart your agent so it picks up the new skills.

• Enable developer mode on your Quest headset. Device tools require ADB access, which requires developer mode to be turned on.
• Enable USB debugging. In the headset, navigate to Settings > System > Developer and enable USB debugging.
• Check your USB cable. Use a USB-C data cable, not a charge-only cable. If the device isn’t recognized, try a different cable or port.
• Allow the connection. When you first connect via USB, the headset prompts you to allow the computer. Put on the headset and accept the prompt.

• Check the URL format. When using fetch_meta_quest_doc, the URL should start with https://developers.meta.com/horizon/llmstxt/documentation/. Use the search_doc tool first to find valid page URLs.

• Call get_perfetto_context first. This tool must be called before using other performance analysis tools like load_trace_for_analysis, trace_thread_state, or run_sql_query.