mcpbeat

Dittu MCP Server

io.github.BorisGujvin/dittu
answering

Dittu is answering right now. Last checked 1 min ago. It exposes 12 tools. Last commit 9 Jul 2026.

Turns a phone into a camera+Bluetooth remote so AI assistants can see and control any PC.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
12
Tools
read from the server
886 ms
Response time
average over 24h
0
Stars
last commit 9 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add dittu --transport http https://app.dittu.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dittu": {
      "url": "https://app.dittu.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.dittu]
url = "https://app.dittu.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dittu": {
      "url": "https://app.dittu.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "dittu": {
      "url": "https://app.dittu.org/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

take
take_screenshot
Capture 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_crosshair
Capture 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).
take_screenshot_with_grid
Capture 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.
corners
get_corners
Get 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_corners
Update 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.
click
click
Click at normalized screen coordinates. nx, ny: float 0.0000–1.0000 where (0,0) = top-left, (1,1) = bottom-right.
double
double_click
Double-click at normalized screen coordinates.
key
key
Press 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])
move
move_mouse
Move mouse cursor to normalized coordinates WITHOUT clicking. nx, ny: float 0.0000–1.0000.
raw
get_raw_screenshot
Capture 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.
scroll
scroll
Scroll the mouse wheel. delta: number of ticks. Positive = scroll down, negative = scroll up.
type
type_text
Type text on the computer keyboard.

Endpoints

URLTransportStateLatencyChecked
https://app.dittu.org/mcp streamable-http answering 870 ms 1 min ago

Dittu — questions

Answers built from our own checks of this server.

What can Dittu do?
It exposes 12 tools, read directly from the server on our last check. Among them: click, double_click, get_corners, get_raw_screenshot, key, move_mouse and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Dittu mostly used for?
Its tools cluster around take and corners. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Dittu working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 886 ms. The bar chart above shows every period we have measured.
How do I connect Dittu?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Dittu need an API key?
No. Dittu completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Dittu?
It answers our handshake in 886 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Dittu open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.