Computer Use vs Dittu
A side-by-side look at the Computer Use and Dittu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Computer Use for os automation work as a local process; choose Dittu for os automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Computer Use when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
mouse_move, mouse_move_smooth, mouse_move_relative.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 52/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 44 | 12 |
| Full listing | View Computer Use | View Dittu |
Tools & capabilities
Computer Use tools 44
mouse_moveMove cursor to absolute coordinatesmouse_move_smoothSmooth cursor movement (human-like)mouse_move_relativeRelative cursor movementmouse_get_positionGet current cursor positionmouse_clickMouse clickmouse_click_atMove and clickmouse_togglePress/release mouse buttonmouse_dragDrag operationmouse_drag_smoothSmooth drag operationmouse_scrollScrollmouse_scroll_directionScroll in directionmouse_scroll_smoothSmooth scroll- +32 more on the listing page
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.
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.
Computer Use
{
"mcpServers": {
"computer-use-2": {
"command": "npx",
"args": [
"-y",
"go-computer-use-mcp-server"
]
}
}
}
Dittu
{
"mcpServers": {
"dittu": {
"url": "https://app.dittu.org/mcp"
}
}
}
Frequently asked questions
Computer Use is categorized under OS Automation and uses a local stdio subprocess. Dittu belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Computer Use for os automation work and Dittu 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.
Computer Use has no declared pricing — check the project's own site. Dittu has no declared pricing — check the project's own site. 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 computer-use-2 and dittu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Computer Use has a quality signal of 52/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Dittu has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.