mcpField
Y
yad-agent-mcp

yad-agent-mcp

Local
github.com/holistisBrowser Automation4Updated 2w ago
Repository

About yad-agent-mcp

yad-agent-mcp is an MCP server that lets coding agents control Yad through its local API and the user's logged-in browser. It supports navigation, page capture, and plain-language browser tasks without running a browser itself.

Key features

  1. 01Check Yad and browser connection status
  2. 02Navigate the controlled browser tab
  3. 03Capture page text, links, URL, and title
  4. 04Run plain-language browser tasks
  5. 05Retrieve the latest task result

Use cases

  1. 01Read information from a logged-in webpage
  2. 02Navigate to a page for an agent task
  3. 03Ask Yad to find information on a page
  4. 04Check the result of a browser task

MCP support

The server connects MCP clients to Yad's local HTTP API over stdio and exposes tools for browser control and page reading. It requires Yad to be installed and running locally; it is not a remote MCP server.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "holistis-yad-agent": {
      "command": "npx",
      "args": [
        "-y",
        "yad-agent-mcp"
      ],
      "env": {
        "YAD_COMPANION_URL": "<YAD_COMPANION_URL>"
      }
    }
  }
}
Run commandnpx -y yad-agent-mcp
Environment variables to set
YAD_COMPANION_URLBase URL of the local Yad companion's HTTP API. Only needed if it runs on a non-default port.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmyad-agent-mcp0.1.1

Tools

5

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

yad-agent-mcp

An MCP server that lets an AI agent drive Yad, a local, privacy-first browser-automation companion, in the user's real, already-logged-in browser.

This is a thin wrapper: it does not run a browser itself. It talks to Yad's existing local HTTP API on 127.0.0.1:3747 over stdio, so any MCP-compatible client (Claude Code, Cursor, Claude Desktop, etc.) can ask Yad to navigate, read a page, or carry out a plain-language browser task, and get the result back.

Local-only by design. This is not a hosted or remote MCP server. It only works on a machine that already has Yad installed and running (extension in Chrome/Edge/Brave, companion app active). If you're looking for a server your agent can call over the internet with zero local setup, this isn't that, and honestly, nothing that drives a user's real logged-in browser session should be.

Requirements

  • Yad installed and running (Chrome, Edge, or Brave extension plus the local companion app)
  • Node.js 20+

Install

npm install -g yad-agent-mcp

Configure your MCP client

Claude Code (.mcp.json or claude mcp add):

{
  "mcpServers": {
    "yad-agent": {
      "command": "yad-agent-mcp"
    }
  }
}

If Yad's companion runs on a non-default port, set YAD_COMPANION_URL (defaults to http://127.0.0.1:3747).

Tools

ToolWhat it does
yad_statusChecks whether Yad's companion is running and connected to the browser. Call this first.
yad_navigateOpens a URL in the browser tab Yad controls.
yad_captureReads the URL, title, visible text, and links of the current page.
yad_run_goalGives Yad a plain-language task ("find the price of the first item", "click the login button") and waits for the result.
yad_last_resultRe-reads the result of the most recent yad_run_goal call.

Yad cannot check out, pay, or place an order without the user's own confirmation, regardless of what an agent asks it to do. This wrapper doesn't add or remove that limit, it's enforced by Yad itself.

Source

Part of the al-yad monorepo. Issues and PRs welcome there.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.