Skip to main content
Glama

PS5 MCP

See and control a jailbroken PS5 from an MCP agent or your keyboard, with live video and audio. It runs on macOS; a headless Linux backend covers capture, screenshots and controller input.

Requirements

  • A jailbroken PS5, currently firmware 13.60. Payload Manager and PS5 Web File Manager are recommended (see Console services).

  • An HDMI capture card connected to the Mac, with HDCP disabled on the PS5 (Settings → System → HDMI → Enable HDCP).

  • macOS 14 or later, with network access to the console.

  • To build: Xcode with a signing account, Homebrew, Python 3.12+, and the tools installed below. The payload uses PS5 Payload SDK v0.43 and LLVM 18.1.8.

Console services

Controlling the console needs only padd running, however it was loaded. These payloads add padd Start/Stop, the game/app list, Install, and file transfers:

Service

Port

Used for

Payload Manager (v0.5.2 tested)

8084

Deploying padd (Start), checking its process is gone (Stop), and installing .elf payloads

PS5 Web File Manager (v1.9 tested; Payload Manager can load it)

8888

Verifying the padd upload and reading its logs (Start/Stop), the game/app list (app and list_apps), and installing .pkg packages

zftpd (v1.6.0 FTP-only zftpd-ps5-v1.6.0.elf; optional)

2120

push/pull over FTP. Add it to Payload Manager's library; it is started when first needed

Without them, load padd.elf with any ELF loader. PS5 MCP expects Web File Manager on port 8888; it moves to the next free port when 8888 is taken. When one of them is not running, the tool or command that needs it says which one. If the CLI or the MCP server reports "no route to host" while other apps reach the console, macOS Local Network privacy is blocking its Python: allow it in System Settings › Privacy & Security › Local Network. A new app build can lose this permission too, even when its switch still shows on. The app window then says "Cannot reach the console", and its button opens that page: turn each PS5 MCP entry off and on again. padd then reconnects by itself.

To add zftpd, download zftpd-ps5-v1.6.0.elf from its releases and add it to Payload Manager's library with uv run ps5mcp install zftpd-ps5-v1.6.0.elf (or Payload Manager's web page). Any library payload named zftpd*.elf is used: zftpd.elf if there is one, else the highest version. Do not run it yourself: push and pull start it when they first need it. Without zftpd, push is slower and pull copies single files only.

Related MCP server: PS5 MCP

How it works

  • padd is a payload running on the PS5. It creates a virtual DualSense and accepts controller input over TCP port 9305.

  • The PS5 MCP app captures HDMI video and audio, owns the connection to padd, and provides keyboard controls, payload Start/Stop, status, and install/uninstall. It talks to Payload Manager and Web File Manager only for the tasks listed above.

  • The MCP server connects agents to the app's local API. Multiple agent sessions and the keyboard can share the console.

Setup

brew install llvm@18 ffmpeg mpv uv xcodegen cmake ninja pkg-config
make bootstrap      # pinned SDK and Python environment
make check          # lint, tests, payloads, and the macOS release app

The release app is built at build/PS5 MCP.app. It is signed ad hoc, so macOS asks for its permissions again after each rebuild. To keep them, sign with your Apple team: make app DEVELOPMENT_TEAM=… APP_BUNDLE_ID=… or app/Configuration/LocalSigning.xcconfig (copy the .example). Quit the app before rebuilding. make install builds the app, waits for agents that hold the console, replaces and restarts /Applications/PS5 MCP.app, and removes the copies under build/. The restarted app reconnects to the console; no other make target contacts it.

Usage

  1. Point it at the console: export PS5_HOST=192.168.1.20 (your PS5's IP address). There is no default. The CLI commands also take --host. In the app, set the address in Settings (⌘,). The app saves it and reconnects to it at once. When the app starts, --host and PS5_HOST win over the saved address.

  2. Open the app: uv run ps5mcp view or open --env PS5_HOST=$PS5_HOST "build/PS5 MCP.app". Allow camera, microphone, local network, and Documents access when prompted. In Settings (⌘,), select your video and audio devices (or No audio) and click Apply & Restart Capture. Device selections are saved by ID; no capture hardware is selected by default. Refresh Devices updates the list after plugging in a card. You can restart capture without disconnecting MCP clients; stop and save any video recording first.

  3. Start padd with Start padd… in the sidebar or uv run ps5mcp padd start, once per console boot. The app answers the user-selection dialog automatically. If your DualSense turns off, press its PS button and select your user again. To answer the dialog yourself, see Pick users by hand. The sidebar's status line shows the running padd version and, when make built a newer one, "update available": Update in the ⋯ menu (or uv run ps5mcp padd update) stops padd and starts the new build.

  4. Control the console from the app window or connect an MCP client (see MCP clients).

  5. Stop padd with Stop padd… in the ⋯ menu or uv run ps5mcp padd stop before turning off the console. Killing it through Payload Manager can leave a phantom controller until reboot.

The MCP server starts the app when needed, headless by default (PS5MCP_VIEW=1 shows the window). Closing an MCP session leaves the app running; quitting the app releases input and leaves padd running. The server and the ps5mcp CLI start /Applications/PS5 MCP.app when it is installed, else build/PS5 MCP.app; PS5MCP_APP=<path to the .app> picks another one. ps5mcp capture stop then start keeps the window open if it was.

Some console screens stop the HDMI signal to the capture card (seen on a few game and app pages). The window then shows "No HDMI signal" over the last picture, and snapshot fails with "No video for N s". The picture comes back when the console leaves that screen. Restarting the app does not help.

MCP clients

Every client runs the same server from this checkout: uv run --project <repo> ps5mcp-server, with PS5_HOST set. Use the full path to uv (command -v uv) if the client does not have Homebrew on its PATH.

Claude Code:

claude mcp add ps5 -e PS5_HOST=192.168.1.20 -- uv run --project /path/to/ps5-mcp ps5mcp-server

Codex: add this to ~/.codex/config.toml (or run codex mcp add ps5 --env PS5_HOST=192.168.1.20 -- uv run --project /path/to/ps5-mcp ps5mcp-server and add the timeouts after). Installs and file transfers can take minutes, longer than Codex's default tool timeout.

[mcp_servers.ps5]
command = "/opt/homebrew/bin/uv"
args = ["run", "--project", "/path/to/ps5-mcp", "ps5mcp-server"]
startup_timeout_sec = 60   # the first start can launch the app
tool_timeout_sec = 600     # install, push, and pull

[mcp_servers.ps5.env]
PS5_HOST = "192.168.1.20"

Other clients that read a JSON config: see examples/mcp.json.

Check the setup with claude mcp list or codex mcp list, then /mcp in a session. Agents from all clients share the console through the same claim and queue (see Sharing the console). A running session keeps the server code it started with; restart it after updating this checkout.

Live window and keyboard

The window shows live video and audio. The sidebar shows what is used most, and a message only when something needs you:

  • Status line: the connection and padd version. Click it for the details and the video source. Under it, messages appear for an agent holding the console, a controller dialog, no signal, or padd not connected, with the action to take.

  • Remote Play: only when Remote Play is the video source: its status, Reconnect and Type…. Set Up and Forget are in Settings.

  • Capture: save a snapshot as PNG (⌘S), and record the picture and sound to an MP4 (⇧⌘R). Under them, pick a saved button recording and play it, or record your button presses (⌘R). These are the same files that agents use with play_recording. Snapshots and videos use one folder, set in Settings. Stop asks where to save the video, starting in that folder; quitting while recording saves it there.

  • Console: Home, the PS button, and close the running game/app.

  • Launch: pick an installed game/app and launch it (⌘L). The list comes from PS5 Web File Manager and is cached in titles/.

  • Controller: the bottom row. + adds a virtual controller, up to four (see More players). With several, click one to send the keyboard's and agents' input to it (⌘1 to ⌘4), and − on the selected one removes it.

  • ⋯ (More): Release all input (⌘.), Force release agent…, Claim and queue…, reload games/apps (⇧⌘L), install a .pkg package or add an .elf payload to Payload Manager, uninstall checked games/apps (padd 1.3), and Start, Update and Stop padd. Update is enabled only when padd runs another version. For titles ShadowMountPlus manages, uninstalling also deletes their source folder or image through ShadowMountPlus, so its next scan does not install them again.

The menu bar has every command, in the Console, Capture, Controllers, Video Source and View menus.

The toolbar's keyboard button, ⌃⌥K from any app, or View › Show Keyboard Panel shows a floating panel with the controller's keys. It floats over all windows unless you turn that off in Settings. Keys reach the PS5 only while the video has focus, and the panel says when they do not. Dimmed keys (Share, touchpad left and right) are not mapped yet.

Holding a key holds its button and gives you priority over agents; releasing it returns control.

Toggle the sidebar with ⌥⌘S, video with ⌥⌘V, and audio with ⌥⌘M. Video and audio preferences persist. Hiding video keeps capture running; closing the window silences audio but keeps the app and API running. Quit with ⌘Q or uv run ps5mcp capture stop.

Keys

Pad

Arrows

D-pad

Enter / Space

Cross

Backspace / Esc

Circle

[ / ]

Square / Triangle

Q / E, Z / C

L1 / R1, L2 / R2

WASD, IJKL

Left stick, right stick

X, M

L3, R3

Tab, T

Options, touchpad click

H

Home screen

Features

MCP tools

Feature

Tools

Capture and status

snapshot, status, show_viewer, frame_meter, measure_frame_rate

Controller input

press, hold, stick, trigger, touchpad, sequence, release_all

Console apps

home, close_app, launch, list_apps, install, uninstall_apps

More players

connect_controller, disconnect_controller, use_controller

Remote Play only

type_text, close_keyboard

File transfer

push, pull

Visual automation

save_template, list_templates, wait_for, wait_for_change

Recording

record_start, record_stop, list_recordings, play_recording

Sharing

claim_console, release_console, controller_ready

Input tools can return a frame with snapshot_after_ms. ps_button presses the PS button (a tap opens the control center) and home suspends the running game; use press("circle") to back out of system screens. With Remote Play as the video source, type_text fills the text field whose on-screen keyboard is open. A game takes input only from the controller that launched it, so launch games with launch to control them through the MCP. After claim_console, controller_ready checks that padd holds a neutral controller, and press(..., require_claim=True) presses only while the claim is still yours.

More players

To test local multiplayer without real controllers, padd runs up to four virtual controllers (padd 1.9; two before it). Controller 1 is the foreground user's (player 1), and each added one is for another signed-in user. Input from the keyboard, the API and MCP agents goes to the selected one.

  1. Sign the other users (or guests) in on the console. status() lists them under payload.login_users, and the ones with no controller yet under payload.controllers.available. Without a real controller, a new controller can sign someone in: + offers the users the app has seen signed in before, or call connect_controller(user_id=<id>).

  2. Click + next to Controller in the sidebar (⌥⌘N), or call connect_controller(), or run uv run ps5mcp pad controller connect. With a choice of users, + shows a menu. The new controller is selected, so the next input goes to it.

  3. The console asks "Who's using this controller?" for it. The picker opens on the first signed-in profile, not on the controller's user. The app moves to that user's profile and answers it there, which also signs in a user who was signed out.

  4. Click the controller to drive in the sidebar (⌘1 to ⌘4), or call use_controller(1) to use_controller(4), or run uv run ps5mcp pad use 1. The others are released.

  5. Launch the game with launch. It always starts the game for the foreground user, so controller 1 owns it.

− removes the selected controller, or call disconnect_controller(3), and input goes back to controller 1 if it was selected. The others keep their numbers. The choice is saved in the state folder. After padd restarts the same users come back in order, so numbers may close up. Four controllers worked in a split-screen game on 13.60 (see findings).

On the home screen the console follows one user's controller. An added controller that presses a button there gets "To take over control, press and hold the PS button": hold P, or Option-click PS in the sidebar, for one second.

Pick users by hand

To answer "Who's using this controller?" yourself, turn on Controllers › Pick Users by Hand (also in Settings). The app then presses nothing when you start or update padd, or add a controller, in the window. The sidebar asks for your answer: move with the arrow keys and press Enter in the window. Controllers that agents add through the MCP or the CLI are still answered by the app.

This is how you give padd's controller 1 to a user other than the one on your DualSense: pick that user when padd starts, and the DualSense stays on.

The app reads which profile you pick, and padd 1.10 records it, so the sidebar and status() name the user who has the controller. If you pick a user who already has a virtual controller ("Switch Controller"), that other controller shows no user. The app records a pick only when it read the name clearly: leave a moment between the last arrow key and Enter. Otherwise the controller keeps the name it was added for, and so does one you give to Add User.

Sharing the console

Several agents can use the console. An agent calls claim_console(reason) so that other agents cannot press buttons, run console commands, or install until it calls release_console(). Another agent that calls claim_console joins a queue. With wait_s, the call returns when the console is free for that agent. A claim ends when its session closes, or after 10 minutes without a tool call. The sidebar shows the agent that has the console and the number of agents in the queue; Claim and queue… (kept up to date while open) shows the holder's full reason, its process and agent (folder, session, command), and everyone waiting. The keyboard and the window's buttons always work. The CLI (ps5mcp pad, ps5mcp padd) is blocked like any agent.

File transfer

push(local_path, remote_path) copies a file or folder from this Mac to the console, and pull(remote_path, local_path) copies one back. Console paths are absolute. A path names the destination itself; end it with / to copy into that folder. Folders are copied recursively. A file with the same size and a destination that is not older is skipped (force=True copies it anyway). A shorter, newer destination resumes when its last 64 KB match the source; otherwise the file is copied again.

Transfers use FTP through zftpd on port 2120. If zftpd is not running, the tool starts it from Payload Manager's library. Starting it counts as a console action, so it is refused while another agent has claimed the console. zftpd cannot be stopped remotely: it runs until the console restarts, and loading it again replaces the running copy. Without zftpd, push sends files one at a time through Web File Manager, and pull copies single files only.

Native uploads set eboot.bin, .prx and .sprx files to 0755 and read back the remote execute bits. Other files with source execute bits are also restored when the upload contains native binaries; ordinary assets are left alone. This check runs even for skipped and resumed files. A rejected SITE CHMOD or an unreadable/incorrect remote mode fails the upload. Native executable uploads require zftpd: Web File Manager cannot provide this permission guarantee.

For folders containing eboot.bin and a PS5 sce_sys/param.json with titleId, push then polls ShadowMount's /api/v1/games until that title is installed, managed, and available from the uploaded source path (up to 90 seconds). Its API must be reachable from this Mac: allow LAN access in ShadowMount's settings, and use PS5MCP_SMP_PORT if its port differs from 10101. The default console-local listener cannot be reached by this check. Failure reports that files may already be uploaded and readiness is unverified; retrying repairs permissions and checks registration again. Within this MCP server session, launch blocks titles whose upload is still running or failed its checks. Other sessions and the console's own launcher do not share this guard. Uploads without a recognized manifest report registration as unverified. These checks prevent the reported execute-permission failure; they do not prove a title will boot.

The .pkg installer follows a separate Web File Manager upload and install-task path; it does not upload unpacked title executables through FTP. Package installs have not been validated for this reported issue. Existing titles are not changed automatically. A read-only permission audit can use FTP MLSD's unix.mode or Unix LIST for eboot.bin and native modules, then scope any repairs to the identified files.

Variable

Effect

PS5MCP_FTP=0

Remove the push and pull tools

PS5MCP_FTP_AUTOSTART=0

Never start zftpd (for example, during experiments that must not load extra payloads)

PS5MCP_FTP_PORT

zftpd's port (default 2120)

PS5MCP_SMP_PORT

ShadowMount's API port for native-title registration checks (default 10101)

Frame meter

View → Show Frame Meter (⌥⌘F) draws the frame rate, the 1% low, and a scrolling frame-time graph over the video. A video recorded while it runs also gets a CSV with the same name. It has each frame's time as captured, before the correction below. The graph itself is not in the video. To include the meter in snapshots saved with ⌘S while it shows, turn on the option under Capture files in Settings. Agents use the frame_meter tool, then read capture.frame_meter from status. To get one result for a fixed period, agents use measure_frame_rate(seconds).

The capture card delivers a fixed 60 fps, so the meter compares each frame with the one before: a frame counts only if the picture changed. It works only with the capture card, and it has these limits:

  • It cannot see above 60 fps, so it cannot measure 120 fps or 40 fps modes. Frame times are multiples of about 16.7 ms.

  • A game without vsync reads too high, because nearly every captured frame contains new content.

  • A very slow scene may read too low, because its small changes are hard to tell from compression noise.

  • The console and the card run on slightly different clocks, so a steady frame rate can read as one long frame and one short frame, next to each other or with one normal frame between them. The meter counts them as even frames. A real frame one refresh late that then catches up looks the same, so the meter does not show it.

  • A screen that barely changes reads "static", and so does a real stall longer than about a second.

Browser viewing

uv run ps5mcp stream serves live MJPEG video at http://127.0.0.1:8090/ (about 10 fps). Add --bind 0.0.0.0 to view from another machine, or set PS5MCP_STREAM_PORT=8090 to start it with the MCP server.

Recording

Record keyboard input with uv run ps5mcp control --record menu-dance (Ctrl-C to finish), then replay it with uv run ps5mcp play menu-dance. Agents can use the recording tools above. You can also record and play from the app window. Recordings and templates live in ~/.local/state/ps5-mcp/.

Other commands

uv run ps5mcp snapshot -o frame.png        # capture a frame
uv run ps5mcp pad press right              # send a button press
uv run ps5mcp pad home suspend             # return to the home screen
uv run ps5mcp pad close                    # close the running game
uv run ps5mcp pad launch PPSA06654          # launch a title
uv run ps5mcp pad uninstall PPSA06654       # uninstall a title (padd 1.3)
uv run ps5mcp pad controller connect       # add a controller for the next signed-in user, send input to it
uv run ps5mcp pad controller connect 480174124 # ... for that user; one who is not signed in gets the sign-in picker (padd 1.8)
uv run ps5mcp pad use 1                    # send input to controller 1 (to 4)
uv run ps5mcp pad controller disconnect 3  # remove controller 3
uv run ps5mcp install game.pkg             # install a package (or an .elf payload; --run starts it)
uv run ps5mcp push build/title /data/homebrew/FAKE00001   # copy a folder to the console (zftpd)
uv run ps5mcp pull /data/playden/logs ./logs/              # copy a folder from the console (--no-start, --force)
uv run ps5mcp padd status                  # payload version (running and bundled), uptime, and counters
uv run ps5mcp latency                      # measure input-to-frame latency

For development without a capture card, use --video synthetic or --video file:PATH when launching the app, or set PS5MCP_VIDEO for the server. Close QuickTime/OBS before capturing: only one process can own the card. Explicit --video/--audio arguments override saved devices for that launch. Python launchers also accept PS5MCP_VIDEO/PS5MCP_AUDIO; --audio none or PS5MCP_AUDIO=none disables audio. If a device is missing, the app stays open: reconnect it or choose another in Settings, then apply the selection. Changing capture devices does not require restarting the MCP server processes managed by your MCP clients.

The ffmpeg fallback requires an explicit device: uv run ps5mcp capture start --backend ffmpeg --video "DEVICE NAME", followed by uv run ps5mcp view --backend ffmpeg. Run it from a regular terminal with camera and microphone permission. Use uv run ps5mcp devices to list devices and --audio "DEVICE NAME" to enable audio. Its legacy format defaults are 1080p, 60 fps, and uyvy422; cards that do not support that mode require adjusting the FFmpeg capture settings.

Remote Play (in development)

The native app also has a LAN Remote Play source and a TV-assisted offline-account setup wizard. It replaces capture-card video/audio while padd continues controlling the console. Live 1080p video/audio and automatic recovery are verified on the existing 13.60 test account; full replacement acceptance remains pending; see setup, validation status, and recovery. Chiaki-ng is pinned as a submodule and built statically for the app. PS5 MCP now uses AGPL-3.0-only; dependency notices retain their upstream licenses.

Linux

A headless Python hub runs the same MCP server on Linux: shared V4L2/FFmpeg HDMI capture or PBS video over the network, screenshots, a local MJPEG browser viewer and padd controller input. Audio, the window and keyboard control, Remote Play and the frame meter are not available there, and a person must answer controller-assignment prompts; see What works on Linux. Physical 1080p60 capture and short controller actions have been tested on the console. See Linux setup, capture results, controller behavior and limits and controller results.

Hardware runs

These commands contact the console. Quit the app before running soak or killtest.

uv run ps5mcp padd soak --minutes 10
uv run ps5mcp padd killtest

Runs are archived in results/ with firmware, loader version, payload hash, logs, and snapshots. Unfinished runs stay marked incomplete.

Development

Versions. pyproject.toml holds the one version of the app and the MCP server; make passes it to the app, with the commit count as the build number, and copies build/padd.elf into the app, so the app always deploys the padd it shows. padd has its own version (PADD_VERSION in payload/padd.c, bumped with every behaviour change), shown next to the app's: 0.6.0 (padd 1.4) in About PS5 MCP and ps5mcp --version. Bump the app version for every release that ships, including a new padd, and tag it v<version>.

Findings · App API · Virtual-pad ABI · Wire protocol · PS button and app control

License

AGPL-3.0-only, see LICENSE. Code written before the Remote Play source keeps its MIT notice in third-party/PS5-MCP-MIT-NOTICE.txt; dependencies keep their own licenses (notices). The virtual-pad interface values come from FGG-XSense and the launch parameter layout from zftpd; this code is a separate implementation.

100% vibecoded

This project is 100% vibecoded with AI coding agents. It's experimental, may contain bugs, and comes with no guarantees. Use at your own risk.

Available Tools

24 tools
close_appA

Close the running game or app (unsaved progress is lost). The console returns to the home screen.

Inputs: snapshot_after_ms.

holdC

Hold several buttons together for duration_ms, then release them.

Inputs: buttons (required), duration_ms (required), snapshot_after_ms.

homeA

Go to the PS5 home screen (stands in for the PS button, which the pad cannot send).

method: "suspend" (suspend the running game, as the PS button does), "system" or "shellcore". From system screens such as Settings, press circle instead.

Inputs: method, snapshot_after_ms.

installA

Install a file from this Mac onto the console.

path: a .pkg package (uploaded through Web File Manager to /data/ps5-mcp/pkg, then installed; can take minutes) or an .elf payload (added to Payload Manager's library). run=True also starts the .elf once.

Inputs: path (required), run.

launchA

Launch an installed title by id (e.g. PPSA01325). list_apps() shows what is installed.

A game takes input only from the controller that launched it: launch it here to control it, because a game the user started with their own controller ignores this pad (and one launched here ignores theirs).

Inputs: title_id (required), snapshot_after_ms.

list_appsC

Installed title ids (from /user/app on the console).

Inputs: no named parameters.

list_recordingsC

Saved recordings with their length.

Inputs: no named parameters.

list_templatesC

Saved template names.

Inputs: no named parameters.

play_recordingC

Replay a saved recording with its original timing (up to 5 minutes).

Inputs: name (required), snapshot_after_ms.

pressB

Press and release one button (e.g. cross, circle, up, options). Optionally return a frame afterwards.

Inputs: button (required), hold_ms, snapshot_after_ms.

record_startA

Start recording every input (agent tools and the keyboard in the viewer) as timed steps.

Inputs: no named parameters.

record_stopB

Stop recording and save it under name (letters, digits, - and _).

Inputs: name (required).

release_allA

Release every button and centre the sticks (agent and keyboard).

Inputs: no named parameters.

save_templateB

Save a region of the current frame (full 1920x1080 coordinates) as a template for wait_for.

Inputs: x (required), y (required), name (required), width (required), +1 more.

sequenceA

Run timed states in order, then release everything.

Each step: {"buttons": [...], "lx"/"ly"/"rx"/"ry": -1..1, "l2"/"r2": 0..1, "duration_ms": N}. A step with no inputs is a pause. Total duration is capped at 60 s.

Inputs: steps (required), snapshot_after_ms.

show_viewerA

Open the live video window for a human (keyboard in that window drives the console too).

Inputs: no named parameters.

snapshotB

Current PS5 screen as a JPEG (scaled to max_width; the source is 1920x1080).

Inputs: max_width.

statusC

Payload link, payload version and counters, capture state and frame age.

Inputs: no named parameters.

stickC

Deflect the left or right stick. x, y in -1..1 (left/up negative), then return to centre.

Inputs: x (required), y (required), side (required), duration_ms (required), +1 more.

touchpadC

Click the touchpad. Coordinates are sent but not yet delivered by padd (touch mapping is unknown).

Inputs: x, y, duration_ms, snapshot_after_ms.

triggerC

Pull L2 or R2 (side: left/right) to value 0..1, then release.

Inputs: side (required), value (required), duration_ms (required), snapshot_after_ms.

uninstall_appsA

DESTRUCTIVE: uninstall installed titles by id (e.g. ["PPSA01325"]); their data is deleted.

Only uninstall what the user asked for by name. For titles ShadowMountPlus manages, their source folder or image is deleted too (otherwise it installs them again). The console refuses while a game is running; close_app first. Removal finishes in the background after each request is accepted. Needs padd 1.3 or later.

Inputs: title_ids (required).

wait_forB

Wait until a saved template appears on screen (or disappears, with gone=true).

Matching is normalised cross-correlation over the whole frame; score 1.0 is identical. Returns where it was found, the score and the frame.

Inputs: template (required), gone, min_score, timeout_ms.

wait_for_changeB

Wait until the screen changes (mean luma difference >= threshold on a 32x18 grid); returns the new frame.

Inputs: threshold, timeout_ms.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools split cleanly into input emulation, recording, vision/template matching, and app management, with distinct purposes. Minor overlap between press/hold/sequence and between wait_for/wait_for_change, but the descriptions clearly differentiate each.

    Naming Consistency4/5

    Almost entirely lowercase snake_case with predictable verb_noun or noun forms (record_start, list_recordings, save_template, wait_for_change, uninstall_apps). A few bare single-word names (snapshot, press, touchpad, home, status) deviate slightly but remain readable and consistent in style.

    Tool Count4/5

    At 24 tools it sits at the heavy end, but the domain genuinely spans capture, input, recording, vision, and app lifecycle, so each tool earns its place. Slightly over-scoped but reasonable for the feature breadth.

    Completeness4/5

    Covers the full lifecycle: capture/view, input, record/replay, template-based waits, app install/launch/uninstall, and status. Minor gaps like no delete for templates or recordings, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate and view the Vega Virtual Device through MCP: press remote keys, take screenshots, record video with sound, wait for screen changes, and check the TV safe area.
      21 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Connects MCP agents to a jailbroken console so they can watch live HDMI video and audio, press buttons through a virtual DualSense, launch or close games, install packages, transfer files, and run visual automation with snapshots and recordings. Multiple agents can share one console through a claim-and-queue system.
      28
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable agents to observe a controlled device's screen from captured video and operate it by sending simulated keyboard, text, scroll, drag, and mouse input. Screenshots can be inspected as numbered visual targets, with dense areas split into zoomed regions so the agent picks a target ID and the server handles coordinate mapping and click execution.
      1
      MIT