Agent MCP Server

If you already use Agent, the agent mcp server is the piece that lets your assistant work with it directly. Browser automation CLI for AI agents.

What the server does

For projects that want to pin the version in package.json:

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Updating — Detects your installation method (npm, Homebrew, or Cargo) and runs the appropriate update command automatically
• Requirements — The Requirements tool exposed by this server
• Wait — The Wait tool exposed by this server
• Clipboard — The Clipboard tool exposed by this server
• Network — The Network tool exposed by this server
• Frames — The Frames tool exposed by this server
• Dialogs — By default, alert and beforeunload dialogs are automatically accepted so they never block the agent. confirm and prompt dialogs still require
• Diff — The Diff tool exposed by this server
• Debug — The Debug tool exposed by this server
• Navigation — The Navigation tool exposed by this server
• Setup — The Setup tool exposed by this server

Credentials and setup notes

• Chrome - Run agent-browser install to download Chrome from Chrome for Testing (Google's official automation channel). Existing Chrome, Brave, Playwright, and Puppeteer installations are detected automatically. No Playwright or Node.js required for the daemon. - Node.js 24+ and pnpm 11+ - Only needed when building from source. -

Installation

The server ships on npm as agent-browser, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agent's toolset — Updating, Requirements, Wait and 8 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agent.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.