3 Automation MCPs

Automation MCP servers

MCP servers for browser automation, scripting, webhooks, and event-driven workflows.

About Automation MCP servers

Automation MCP servers let agents actually do things: drive a browser with Playwright or Puppeteer, inspect a page with Chrome DevTools, run scripts, and chain webhooks. They are the action layer of an agentic system.

All Automation MCP servers

3 servers, ordered by community adoption.

Playwright MCP

Reliable browser automation for AI agents

Automation

A browser automation MCP server built on Playwright. Agents can navigate pages, click elements, fill forms, capture screenshots, and inspect the DOM with deterministic waits and accessibility-aware locators.

browserplaywrighttestingautomation
28,400 76,700 92
Install

Puppeteer MCP

Headless Chrome automation via MCP

Automation

A Puppeteer-based MCP server for scraping, screenshotting, and interacting with web pages. A practical alternative to Playwright when teams already standardize on the Puppeteer ecosystem.

browserpuppeteerscrapingautomation
14,200 48,900 75
Install

Chrome DevTools MCP

Inspect and script the live browser

Automation

Expose Chrome DevTools Protocol commands through MCP. Agents can capture console output, profile performance, manipulate cookies, and execute JavaScript against a live Chrome instance.

chromedevtoolsbrowserprofiling
6,300 19,400 76
Install

How to install a Automation MCP server

  1. Pick a server from the list above and read its detail page.
  2. Copy the install command. Most servers run via npx, uvx, or docker.
  3. Open your AI client's MCP configuration and add the command.
  4. Restart the client and verify the tools appear in the model context.

Need a refresher? Read the MCP guide for the full walkthrough.