DeskManager

MCP DeskManager

DeskManager — MCP Connector

Your own Windows PC as a tool for your AI assistant: files, terminal, browser, desktop applications and email — running on your machine, under your account, with confirmations for anything that cannot be undone.

At a glance
Connector typeRemote MCP server (Streamable HTTP) — one private URL per PC, generated by the DeskManager app
AuthenticationOAuth 2.1 with PKCE (S256). Discovery: /.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server
Runs onWindows 10/11 (the user's own PC). The server component only handles licensing and updates
Tools14 tools, every one annotated with readOnlyHint / destructiveHint
Support[email protected]
Privacyprotime.it/privacy

1. How it works

DeskManager installs on a PC and starts a local MCP server. It opens an encrypted outbound tunnel (Cloudflare) so that the PC is reachable at a private hostname such as https://mcp-xxxxxxxxxxxxxxxxxxxx.protime.it/mcp without opening any router port. The identifier is 20 random lower-case letters and digits (about 1031 combinations), generated by the app, listed nowhere and never reused. An MCP client (Claude, or any OAuth-capable client) connects to that URL, completes the OAuth flow on the user's own machine, and from then on calls tools that execute on that PC. Protime's servers never see tool inputs or outputs.

2. Connecting in five steps

  1. Install DeskManager on the Windows PC (installer from your licence email; it self-installs to %APPDATA%\DeskManager).
  2. Open the DeskManager dashboard → Connection. On first start, sign in with Google and add the licence key. The tunnel registers itself and the page shows the PC's MCP URL and its Connection Keys.
  3. In Claude: Customize → Connectors → + Add → Add custom connector, paste the URL.
  4. Claude opens the authorisation page served by that PC. Paste a Connection Key from the dashboard and confirm. Done — the connection persists across conversations.
  5. In any chat, call help() once: it returns the overview and, from then on, every wrong command answers with the exact help call to fix it.

3. Tools

Read tools and write tools are deliberately split, so a client can allow the first group freely and gate the second.

ToolWhat it doesHint
helpReference guide; help(section=…, query=…) returns only the entries you needread-only
systemSessions, PC status, screenshots, health, clipboardread-only
terminal_reader / terminal_executorRead output of persistent shell tabs, or wait server-side until a word appears, a port or URL answers, a file exists or a process ends (at most 4 minutes per call) / run commands and scripts (PowerShell, cmd, WSL). Bash scripts run from a file, so variables and quotes reach bash exactly as writtenread-only / destructive
file_reader / file_writerRead, list, search, diff any file type (PDF, DOCX, XLSX, images…) / write, edit, move, trash, downloadread-only / destructive
browser_reader / browser_actionBuilt-in browser (Playwright) or, with the optional extension, the user's own Chrome: read pages, elements, tables; click, type, fill forms, wait, dismiss dialogs. Every action also reports what it changed, in the same call (observe): the page, the focused field and its real value, dialogs and controls that appeared, and whether a click opened a new tab or left the page unchanged. In the user's Chrome, clicks, key presses and mouse hovers are delivered as real input through Chrome's debugger channel — Chrome shows its yellow "DeskManager is debugging this browser" bar for the duration of each action, and the user can stop it from there. Logging in uses the passwords Chrome already stores, or "Sign in with Google": the assistant only sees account names, Chrome fills the password, and every login requires the user's confirmation. Chrome's own dialogs (password warnings, permission prompts) are detected and can be closed. The assistant stays on the tab it attached to and never follows the user's focusread-only / destructive
software_reader / software_actionDesktop UI automation via Windows UI Automation: read windows and controls / click, type, launchread-only / destructive
email_reader / email_writerIMAP/SMTP accounts the user configures locally: read, search across one or every mailbox in a single call / send, reply, move — sending always happens in two steps (draft, then explicit confirmation)read-only / destructive
phoneThe user's paired Android phone: send a notification, a file or a text, ask a question, set a timer, watch a terminal tab for a keyworddestructive
panelAn interactive card inside the chat (MCP App, also in the mobile apps) whose HTML the assistant writes for the task at hand: a file browser, a photo gallery, a chart on a file's data, a form, a system dashboard, an upload or download button. Nothing is pre-built: the card talks to the PC through a small API (files in the allowed folders, upload from the phone, one-time download links, screenshot, system status), and every tap is logged on the PC. Terminal, browser and apps are not reachable from a card: it asks the assistant insteaddestructive

4. Safety model

5. Example session

help()                                   → overview + how to open a session
system(action='session', command='new')  → session_id
file_reader(session_id=SID, action='list', path='C:\Users\Test\Documents')
browser_action(session_id=SID, action='open', url='https://example.com')
browser_reader(session_id=SID, action='extract_table')
terminal_executor(session_id=SID, command='Get-Process | Sort CPU -desc | Select -First 5')

6. Testing the connector (for reviewers)

A dedicated test PC (a Windows 11 virtual machine with sample documents, a configured browser and a shell) is available for review. Request credentials and the test MCP URL at [email protected]; a licence and the OAuth login for the test machine are provided within one business day. The whole flow in section 2 takes under ten minutes on that machine.

7. Endpoints

PathPurpose
POST /mcpMCP endpoint (Streamable HTTP). Unauthenticated requests receive 401 with WWW-Authenticate: Bearer resource_metadata=…
GET /.well-known/oauth-protected-resourceRFC 9728 resource metadata
GET /.well-known/oauth-authorization-serverRFC 8414 authorisation server metadata (PKCE S256, authorization_code)
GET /mcp/authorize, POST /mcp/tokenOAuth authorisation and token endpoints, served by the user's PC
GET /healthLiveness
GET /api/panel/download/<token>One-time download link created by a panel (expires after ten minutes; the token is the only key)

8. Support and reporting

Email [email protected]. Security reports are read first; please include the DeskManager build number shown in the dashboard.