The Quest toolchain: one CLI, two interfaces, one channel per agent
(Meta VR CLI) is a single tool with two faces: a command line, and a
stdio
MCP server an agent drives on its own. Everything below is available
through both — the CLI names are given because they are also the fallback when
no MCP server is configured.
Read
references/research-navigation.md
when planning research, choosing a
capture/automation path, handling conflicting sources or working without a tool.
Resolve the executable and inspect that version's help before using this dated
command map; generated companion instructions may describe a different version.
For a whole-product roadmap or stage audit, use
; a single technical task stays with this owner. If absent, identify the current stage, its evidence and the next prerequisite inline.
Read
references/source-research.md
for current-source discovery, unavailable Markdown, conflicting requirements, versioned API indexes and existing CLI/MCP registrations.
Install it once, through one channel
| Channel | Command | Updates |
|---|
| Native installer (preferred) | curl -fsSL https://developers.meta.com/horizon/install-cli/ | sh
| , in place |
| npx, no install | npx -y metavr@latest <cmd>
| always current |
| npm global | | never on its own — needs |
Two of these installed at once is a version split waiting to be read as a bug:
on this estate
(1.3.2.2.2) and
(npm 1.3.2) both answered to
, and PATH order decided which. Check with
and keep one.
Sign in —
, verify with
. It unlocks the
Store commands;
covers unattended automation.
is the trap, not the setup
installs skills, configures MCP servers and installs agent plugins. With
no target flag it means , and "all agents" is its own fixed
list, not the agents you have. Run inside a project directory it writes one
tree per agent
into that directory.
Measured 2026-09-20 in a game repository: 29 skills × 25 directories =
4129
files, 47 MB, untracked, uncovered by
— and the next
committed the lot into the product.
On this estate, inspect the gateway/plugin registration before setup. A new
standalone metavr stdio server belongs in the gateway;
examples configure agents directly and are not the default here. If a selected
host installation is needed, inspect
and the target paths
first. Do not ignore project-owned
or other existing files broadly.
The command map
| Job | Command |
|---|
| What is attached | / / |
| Pair over Wi-Fi | (USB first), , |
| Make a device test-stable | metavr device configure-testing
|
| Install / launch / stop a build | / / |
| Logs | (logcat), |
| Screens | metavr capture screenshot
|
| Files on device | / / / |
| UI automation | / / / / |
| Performance | / / / / / |
| Docs and API reference | / / |
| 3D assets | metavr asset search "<thing>"
|
| Store distribution | / / / ; |
| Emulator | (SpatialSim) |
| Managed tools | / |
| Setup report | |
reports
installed software only — it does not test device
connectivity, sign-in or MCP wiring. A green doctor with no headset attached is
still a machine that cannot run anything.
The MCP server, and how it ends up registered twice
is the stdio server. Meta's plugin may own its
registration; otherwise the operator's configured gateway can expose it.
Do not register both. On this estate, new standalone stdio/static-token servers
go through
~/.config/agentgateway/servers.yaml
and the existing generator/migration
flow; OAuth protected-resource servers stay at the agent. Plugin-managed MCP
stays with the plugin. A direct
is appropriate only where the selected
deployment policy calls for it, not a universal project setup recipe.
shows whether the XR Operator proxy is installed and
federated into metavr's own MCP server — when it is, a running XR app can be
inspected through the same connection; no second server to register.
Meta's 29 skills, and what this pack adds
Meta publishes them at
github.com/meta-quest/agentic-tools
(plugin
, also on
,
, Cursor, Codex, Gemini).
The split is worth knowing before wondering which one to reach for:
| Meta's skills | Count | Owner of the lane |
|---|
| 12 | Unity — this pack does not duplicate them |
| , , | 3 | doc verification and CLI reference |
| , , | 3 | driving a specific profiler |
| , | 2 | store mechanics |
| , , , , , others | 9 | other build paths |
This pack answers the questions that sit above a tool: which lane a project
is on, which number to read, what to measure, what the Store will reject. Where
a Meta skill drives the tool, use it — and say which one did the work.
No headset on the desk
- (Meta XR Simulator) and () run app logic on
the machine. They check supported simulated behavior and integration.
- They cannot answer a performance question: no real GPU, no thermals, no
compositor. See .
metavr device browser <url>
Managed developer tools
metavr tools install <name>
fetches and installs;
shows
versions and what is present. What each is for — including which need a headset
— is in
references/tool-matrix.md
.
Hygiene, because the estate pays for it later
- One channel per agent. A plain copy under beats
the plugin of the same name and serves its frozen version forever.
- Never vendor skills into a product repository. They are installed on the
machine; a repo copy is 47 MB of a third party's text your CI now lints.
- Skills and plugins load at session start — restart the agent after
changing either, or it keeps the old set.
- After any install or removal, the check that must print nothing:
bash
for d in ~/.claude/skills/*/; do n=$(basename "$d"); \
[ -e ~/.claude/plugins/marketplaces/"$n" ] && echo "SHADOW: $n"; done
CLI surface read from at 1.3.2.2.2 on 2026-09-20; the install
and init behaviour was measured on this machine the same day.
Triggers
More phrases that route here: "adb to Quest" / "adb к шлему", "XR Simulator" / "симулятор",
"no headset" / "нет шлема", "metavr init", "Meta VR CLI", "Quest MCP" / "MCP для Quest",
"install the APK" / "поставить apk на шлем", "developer mode" / "режим разработчика", "which
Quest tools are installed" / "что установлено для Quest", "hz- skills" / "скилы Meta".