Let an AI assistant run the support session.
VVDesk gives an AI assistant the tools you use yourself: find a desk, open a session in the background, look at the screen, click and type, run a command and collect the logs. You say what is wrong — it works through it and tells you what it found.
Works with Claude Code, Claude Desktop and other assistants that support MCP — or any assistant that can run a command in a terminal.
- You
The receipt printer at Store 1 stopped printing. Find out why and fix it.
First I’ll see which desks are online.
vvdesk desks --filter online3 online: Store 1 · Till, Store 2 · Till, Back office serverI’ll open Store 1 in the background, so the cashier’s screen does not change.
vvdesk connect 615220937 --hiddenSession live · hidden · the desk let us in with its unattended passwordHere is the till’s screen.
vvdesk screenshot 615220937 till.pngSaved till.pngThe “Receipt” queue has 14 stuck documents. I’ll clear them and restart the print spooler.
vvdesk exec 615220937 --shell powershell --cmd "Get-PrintJob -PrinterName Receipt | Remove-PrintJob; Restart-Service Spooler"Exit code 0 · shown at the desk · written to the audit logChecking that it prints again.
vvdesk screenshot 615220937 after.pngSaved after.png — the queue is empty, the test receipt printedFixed. 14 receipts were stuck in the “Receipt” queue on Store 1 · Till. I cleared them and restarted the print spooler; a test receipt printed. Nothing else was changed.
Ready in three steps
- 1
Install VVDesk and sign in
The assistant uses the VVDesk on your own PC — your account, your plan and your address book. No extra keys, no extra server.
- 2
Connect your assistant
Add VVDesk to an assistant that supports MCP with one command, or let the assistant run the vvdesk command line itself.
claude mcp add vvdesk -- vvdesk mcpNext updateThe MCP server (vvdesk mcp) comes with the next VVDesk update. The vvdesk command line works today.
vvdesk.exe is in the VVDesk folder, %LocalAppData%\VVDesk\current. Use its full path if that folder is not on your PATH.
- 3
Say what is wrong
Describe the problem in your own words. VVDesk tells the assistant to look before it clicks and to ask you before it changes or deletes anything.
What the assistant can do
Look
- See the address book and which desks are online
- Take a fresh screenshot of a desk — in a hidden session too
- Read this PC’s VVDesk activity log
Act
- Open and close sessions, in the background if you like
- Move, click, scroll, type and press key combinations
- Run a command in cmd or PowerShell and read its output
Diagnose
- Run the desk’s diagnostics: network, routes, public address
- Collect the desk’s VVDesk logs into one zip
- Report back in plain words, with what it changed
The rules stay with the desk
An assistant gets no more than you have. Everything it does goes through the VVDesk signed in on your PC, and every desk applies its own rules.
The desk still decides
An assistant connects the way you do: the person at the desk accepts, or the unattended password set on that PC lets it in.
Commands only where allowed
A command runs only on PCs whose owner turned on remote commands. It shows on the desk’s screen and goes into the audit log.
Your account, your limits
Your plan, your role and your address book apply. A hidden session still appears in your Sessions list and in the log.
Know where screenshots go
Screenshots and command output go to the AI assistant you chose, under its provider’s terms. VVDesk itself still cannot see your sessions.
Things to ask
- “Check that every till is online and its printer is ready.”
- “Store 2 says the scale shows the wrong price — have a look.”
- “Collect the logs from the back office server and tell me why it restarted.”
- “Find the PC in the Stores group that is running out of disk space.”
Try it with the 14-day Team trial.
Install VVDesk, sign in, and give your assistant its first desk.