Playwright MCP
// Definition
The official MCP server from Microsoft's Playwright team that gives AI assistants browser automation capabilities. The assistant calls structured tools (browser_navigate, browser_click, browser_type, browser_snapshot) over the protocol; the server drives a real browser via Playwright. Used for AI-driven exploratory testing, bug reproduction, test scaffolding, and debugging — augmenting rather than replacing deterministic Playwright test suites.
// Related terms
Model Context Protocol (MCP)
An open standard introduced by Anthropic in late 2024 that lets AI assistants connect to external tools and data sources through a uniform JSON-RPC interface. An MCP server exposes tools (callable functions), resources (readable data), and prompts (templates) to any MCP-compatible host (Claude Desktop, Claude Code, IDE plugins). Build a server once and any compliant client can use it — the protocol is model-agnostic, which makes integrations portable across AI providers.
AI Testing
The use of AI — language models, machine-learning classifiers, and AI-powered platforms — to accelerate testing tasks: generating test code from descriptions, analysing logs and stack traces, suggesting edge cases, healing broken locators, comparing screenshots intelligently, and triaging failures. AI augments QA engineers; it does not replace the judgement, exploration, and risk-modelling work that humans still do best.
Self-Healing Tests
Test automation that captures multiple element attributes during recording (id, class, position, text, accessibility role) and uses an AI matcher to find the closest replacement when the original locator stops working. Reduces locator-rot maintenance for minor UI changes but cannot recover from major redesigns and can silently mis-bind to wrong elements — healed selectors require human review. Common implementations include Mabl, Testim, Functionize, and the open-source Healenium.
Learn more · Playwright MCP
Chapter 1 · Lesson 1: What Is the Model Context Protocol (MCP)