Dittu vs Remote Pc MCP
A side-by-side look at the Dittu and Remote Pc MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
Remote Pc MCPOS AutomationDrive a PC over MCP: shell, files, processes, system stats, screenshots, mouse and keyboard.49FairAuth: api key requiredVerdict: choose Dittu for os automation work over a hosted endpoint; choose Remote Pc MCP for os automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dittu when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
take_screenshot, take_screenshot_with_grid, take_screenshot_with_crosshair.
RChoose Remote Pc MCP when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
REMOTE_PC_MCP_TOKEN. - You want tools like
shell_exec, read_file, write_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Remote Pc MCP | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | REMOTE_PC_MCP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 15 |
| Full listing | View Dittu | View Remote Pc MCP |
Tools & capabilities
Dittu tools 12
take_screenshotCapture the current screen via the Dittu phone camera. Returns a JPEG image. Call this to see what's on screen before acting.take_screenshot_with_gridCapture the screen and overlay a coordinate grid. step: grid spacing (default 0.1, use 0.05 for finer grid on small UI elements). Returns a JPEG image with grid drawn on top.take_screenshot_with_crosshairCapture the screen, crop tightly around (nx, ny), zoom in, and draw a crosshair at exactly that expected position. Use this for screen-corner calibration: move_mouse(nx, ny) near a screen edge, then call this to see whether the actual cursor lines up with the crosshair (where it SHOULD be if calibration is perfect). If the cursor is offset from the crosshair, or missing entirely (edge is cropped out of frame), corners need adjusting — see get_corners/set_corners. nx, ny: the same coordinates you passed to move_mouse. zoom: magnification factor for the cropped region (default 4x).get_raw_screenshotCapture the RAW camera frame — no perspective warp, no crop to the calibrated screen quad. Use this to see exactly what the camera sees before any correction, e.g. when troubleshooting why take_screenshot looks wrong, or before adjusting corners with get_corners/set_corners.get_cornersGet the phone's current screen-corner calibration. Returns {"tl": [nx,ny], "tr": [nx,ny], "br": [nx,ny], "bl": [nx,ny]} — each corner is a normalized point (0.0–1.0) in the RAW camera frame, defining the perspective warp that maps the camera view onto a flat rectangle representing the monitor. These four points are an arbitrary quadrilateral (trapezoid), not a bounding box — adjust one corner at a time without assuming the others move symmetrically.set_cornersUpdate the phone's screen-corner calibration. Each corner is [nx, ny] normalized 0.0–1.0 in the raw camera frame. tl/tr/br/bl = top-left/top-right/bottom-right/bottom-left of the monitor as seen by the camera (an arbitrary trapezoid due to perspective — not a rectangle). Call get_corners() first to read the current values before nudging one of them.move_mouseMove mouse cursor to normalized coordinates WITHOUT clicking. nx, ny: float 0.0000–1.0000.clickClick at normalized screen coordinates. nx, ny: float 0.0000–1.0000 where (0,0) = top-left, (1,1) = bottom-right.double_clickDouble-click at normalized screen coordinates.type_textType text on the computer keyboard.keyPress a key combination. modifiers bitmask: LCtrl=1, LShift=2, LAlt=4, LWin=8 Common keycodes: Enter=40, Escape=41, Tab=43, Space=44, F4=61, PageDown=78, PageUp=75, Win=227 Examples: Alt+F4 → key(4, [61]) Ctrl+W → key(1, [26])scrollScroll the mouse wheel. delta: number of ticks. Positive = scroll down, negative = scroll up.
Remote Pc MCP tools 15
shell_execRun any shell command — returns stdout, stderr, exit coderead_fileRead a file as text or base64 (binary fallback)write_fileWrite text or binary content to a filelist_directoryList files and directories, optionally recursivesystem_infoOS, CPU, RAM, and GPU stats (NVIDIA GPUs via `nvidia-smi`; absent on non-GPU hosts)start_processStart a long-running command in the background — returns a PIDget_process_outputPoll stdout/stderr of a background process by PIDkill_processTerminate a process by PIDdownload_fileDownload a URL directly to this machinetake_screenshotCapture the primary display — returns base64-encoded PNGclickClick at screen coordinates `(x, y)` — left / right / middle, single or multi-clickmove_mouseMove cursor to `(x, y)`, optionally animated- +3 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dittu
{
"mcpServers": {
"dittu": {
"url": "https://app.dittu.org/mcp"
}
}
}
Remote Pc MCP
No confirmed install command for Remote Pc MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Dittu is categorized under OS Automation and uses a remote HTTP/SSE transport. Remote Pc MCP belongs to OS Automation and uses an install path we have not confirmed yet. Pick Dittu for os automation work and Remote Pc MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Remote Pc MCP has no confirmed install command yet — follow its own setup instructions.
Dittu has no declared pricing — check the project's own site. Remote Pc MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dittu and remote-pc-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dittu has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Remote Pc MCP has 49/100 (Fair) with 0 views, 0 installs and 6 GitHub stars.