mqdh-mcp

Unofficial MCP server for Meta Quest developers. Lets an AI assistant list your developer organizations, apps and release channels, and upload builds (APK/OBB) to a channel such as ALPHA, BETA, RC or LIVE — the same way Meta Quest Developer Hub (MQDH) does.

Not affiliated with or endorsed by Meta. Uploads use Meta's official ovr-platform-util. Org/app/channel lookups use undocumented graph.oculus.com operations that may change without notice.

TL;DR for AI assistants

1. auth_status — confirm a Meta login is available.

2. list_orgs → select_org { org } — pick the developer organization (saved for later calls).

3. list_apps → find the app; list_channels { app } — see channels and latest builds.

4. upload_build { app, channel, apk, dry_run: true } — preview, then run without dry_run.

5. upload_status { job_id } — poll until status is succeeded or failed.

Rules: uploads are drafts unless publish: true. Publishing to LIVE (or copying a build into LIVE) needs confirm_live: true — only set it when the user explicitly asks to ship to the public store. app and org accept an id or a partial name.

Related MCP server: Antigravity Play Console MCP

Tools

channel accepts ALPHA, BETA, RC, LIVE (aliases store, production), a custom channel name, or a channel id.

Example

User: Upload C:\builds\game.apk to the BETA channel of "Space Game" with notes "fixes crash".

→ list_orgs / select_org { "org": "My Studio" }
→ upload_build { "app": "Space Game", "channel": "BETA", "apk": "C:\\builds\\game.apk", "notes": "fixes crash", "dry_run": true }
→ upload_build { "app": "Space Game", "channel": "BETA", "apk": "C:\\builds\\game.apk", "notes": "fixes crash" }
← { "job_id": "a1b2c3d4", "channel": "BETA", "mode": "draft", "status": "uploading" }
→ upload_status { "job_id": "a1b2c3d4" }

Install

Requirements: Node.js 20+, and Meta Quest Developer Hub installed and logged in (open it once so it downloads ovr-platform-util).

git clone https://github.com/thankyoucoinbase/mqdh-mcp.git
cd mqdh-mcp
npm install

Claude Code

claude mcp add mqdh -- node /absolute/path/to/mqdh-mcp/Source/server.js

Claude Desktop / other MCP clients

{
  "mcpServers": {
    "mqdh": { "command": "node", "args": ["/absolute/path/to/mqdh-mcp/Source/server.js"] }
  }
}

Authentication

No separate login: the server reuses your existing MQDH session. Token sources, in order:

1. MQDH_TOKEN environment variable

2. MQDH's odh/mcp-config.json in your app-data folder

3. Windows Credential Manager entry Meta Quest Developer Hub/default

4. metavr auth profile-token

If none work, log in to MQDH or run metavr auth login.

Configuration

All optional; defaults follow the standard MQDH install.

Tested on Windows. macOS paths follow MQDH's layout but are untested.

Security

• Tools never return the access token; it is redacted from upload output.

• ovr-platform-util receives the token as a command-line argument (as MQDH does), so it is visible to other local processes while an upload runs.

• The graphql tool can run mutations as you. Remove it from your client's allowed tools if you don't need it.

How it works

Development

npm test            # offline tests, no login needed
npm run test:live   # read-only tests against your account; never uploads

Project layout and conventions for contributors (human or AI): AGENTS.md.

License

MIT