Dom Query And Element Inspection

via “dom-query-and-element-inspection”

MCP server for Chrome DevTools

Unique: Exposes CDP's Runtime domain for DOM queries through MCP, allowing agents to inspect elements without context switching to browser console. Returns structured metadata (bounding boxes, computed styles) in a single call, reducing round-trips compared to sequential property queries.

vs others: More efficient than Puppeteer's page.$() because it returns computed styles and layout info in one call rather than requiring separate property accesses, reducing network overhead in agent workflows.

via “dom-element-selection-and-querying”

Model Context Protocol servers for Playwright

Unique: Exposes Playwright's locator API as MCP tools with rich metadata responses (bounding box, visibility, attributes), enabling LLMs to make informed decisions about element interaction without trial-and-error clicking, and supporting both CSS and XPath with automatic selector validation

vs others: Returns structured element metadata (visibility, enabled state, bounding box) in a single query, reducing the number of round-trips needed compared to frameworks that require separate queries for element existence, visibility, and interaction readiness

via “dom-query-and-element-inspection”

MCP Server for Browser Dev Tools

Unique: Wraps CDP DOM.querySelector and DOM.getAttributes as MCP tools with structured output, allowing agents to query and inspect elements without writing JavaScript or managing CDP node IDs directly

vs others: More efficient than Puppeteer's page.evaluate() for simple DOM queries because it uses CDP's native DOM domain instead of spinning up a JavaScript context

via “dom-inspection-and-element-selection”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Exposes DOM inspection as an MCP tool rather than requiring the LLM to write JavaScript; abstracts selector computation and element metadata extraction into a single call, reducing the cognitive load on the LLM for page structure understanding.

vs others: Simpler for LLMs than raw Puppeteer.evaluate() calls because it returns pre-structured element metadata and auto-generates stable selectors, reducing trial-and-error in element targeting.