mqdh

Automate Meta Quest Horizon OS tooling via MQDH MCP.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/tuantiensiu/todo-app --skill mqdh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mqdh
Source: https://github.com/tuantiensiu/todo-app/tree/main/.opencode/skill/mqdh
Command: npx skills add https://github.com/tuantiensiu/todo-app --skill mqdh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meta Quest developers need quick access to Horizon OS docs, ADB tooling, and device management. This skill provides a centralized way to interact with the Meta Quest Developer Hub MCP, enabling faster discovery and operational workflows.

Core Features & Use Cases

  • Fetch Meta Horizon OS documentation with fetch_meta_quest_doc.
  • Retrieve the bundled ADB path with get_adb_path.
  • List connected Quest devices with device_list and install APKs with install_apk.
  • Use within development pipelines to search docs, manage devices, and automate deployments.

Quick Start

Install MQDH v6.2.1+ and set MQDH_MCP_PATH, then activate the mqdh skill to fetch docs, list devices, or install APKs on Quest headsets.

Frequently Asked Questions about mqdh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install APKs on Meta Quest headsets from my development pipeline?

To install APKs on Meta Quest headsets, you can use the device_list tool to identify connected devices and then invoke install_apk. This automates deployment directly through the MQDH interface without manual ADB commands.

How do I access Meta Horizon OS documentation programmatically?

You can access Meta Horizon OS documentation by invoking the fetch_meta_quest_doc function. This allows developers to quickly search and retrieve necessary Horizon OS docs within their automated workflows.

Do I need MQDH installed to manage Quest devices and retrieve the ADB path?

Yes, you need MQDH v6.2.1 or higher installed and the MQDH_MCP_PATH environment variable configured. These prerequisites allow the skill to correctly locate the bundled ADB and invoke device management tools.

What is the best way to list connected Quest devices for VR AR development?

The best way to list connected Quest devices is by using the device_list tool provided by the MQDH skill. It queries the Meta Quest Developer Hub to return all active headsets ready for deployment.

Can I retrieve the bundled ADB path automatically without searching my file system?

Yes, you can retrieve the bundled ADB path automatically by using the get_adb_path function. This eliminates the need to manually search your file system for the Android Debug Bridge executable.

What are the limitations of using MQDH for device management and documentation retrieval?

The primary limitation is its strict dependency on MQDH v6.2.1+ and a correctly set MQDH_MCP_PATH environment variable. Without these exact configurations, the skill cannot invoke tools or function correctly.