Yad Agent MCP server

Yad (يد), self-hostable, privacy-first AI browser automation agent

Built by Abdellah Ouadoudi

Website / homepage / live URL

• The YAD website (live landing page): https://yadagent.com, own domain, purchased 2026-08-25, migrated live 2026-08-26. Also live in Dutch as a second language, every page has an -nl counterpart (for example /yad-nl, /yad-business-nl). Served from the same server as before (nginx vhost proxies / to the /yad route on the x402 server). The old https://wazir-x402.duckdns.org/yad URL still works and serves the same content, but yadagent.com is now the canonical one.
• Chrome Web Store listing (install page): https://chromewebstore.google.com/detail/dacfhekkemkiikecbjffmbdcohddodea, live and installable today.
• Microsoft Edge Add-ons: submitted 2026-08-26, in review (Microsoft's own estimate is about 7 business days).
• Brave: supported today, no separate submission needed. Brave installs the same Chrome Web Store extension directly, verified working via a real native-messaging handshake test, not assumed.
• Landing page source lives in site/index.html; the deployed copy lives at /app/euler-liquidator/data/yad-landing.html on the server. nginx config for the domain: /etc/nginx/sites-available/yadagent on the Hetzner box.

Yad ("the hand" in Arabic) is a thin Chrome extension (the Hand) controlled by a locally hosted brain (the Companion). It works inside the user's real, logged-in browser session, learns a task once, and then repeats it deterministically at near-zero cost.

Yad is two separate installs, on purpose. Part A, the extension, from the Chrome Web Store. Part B, the companion, as an npm package: npx yadagent pair (native messaging, pairs with Part A, your real logged-in browser) or npx yadagent serve (standalone, no extension, headless Chromium, your own Ollama instance). See packages/companion/npm-package or the package on npm.

Second account / second profile, run side by side. YADINSTANCE= YADPORT= on setup registers a second, fully independent companion (its own native-messaging host, its own port, its own data files), so a second Chrome profile can pair with it without ever touching the first instance's tabs or session. Point the second profile's extension at it under Settings → Advanced. Without those env vars, nothing changes for a single-instance setup.

Benchmark results (gpt-4o-mini, July 2025):

92% fully correct on 25-task open benchmark · 100% on 5 authenticated tasks · 100% pass+partial · avg 2.7 steps · avg 8.7s per task

→ See Benchmark section below.

Benchmark

Shortened. The full README is on GitHub.