Dom Element Manipulation

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

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

Unique: Wraps Puppeteer's element query and interaction methods (page.$, page.click, page.type) as discrete MCP tools, allowing LLM agents to compose multi-step interactions (find element → extract property → click → wait) without managing Puppeteer's page object

vs others: More granular than Selenium (which requires explicit driver management) and more accessible than raw Puppeteer (no JavaScript knowledge required from LLM client, works via tool schemas)

via “dom-to-text serialization with interactive element indexing”

🌐 Make websites accessible for AI agents. Automate tasks online with ease.

Unique: Uses a Watchdog pattern with event-driven re-serialization instead of full-page re-parsing on every state change, reducing overhead. Implements visibility calculation via viewport intersection, CSS computed styles, and z-index stacking context analysis. Maintains a stable element index mapping across DOM mutations, enabling consistent LLM references even as the page updates.

vs others: More efficient than Selenium's element finding because it pre-computes all interactive elements and their coordinates in a single pass; more accurate than regex-based HTML parsing because it uses actual CSS computed styles for visibility.

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-based element selection and targeting”

Hey HN,Claude Code is pretty agentic now. It writes scripts, calls APIs, uses CLIs. But when something requires actually clicking through a website, it stops and asks me to do it.Problem is, I'm often unfamiliar with these platforms myself. "Go to App Store Connect and generate a P8 key&qu

Unique: Exposes DOM element metadata as structured data through MCP, allowing Claude to reason about page structure programmatically rather than relying solely on visual screenshots or trial-and-error clicking.

vs others: More reliable than coordinate-based clicking because it targets semantic elements rather than pixel positions, making automation resistant to layout changes or responsive design variations.

via “dom-element-interaction-and-manipulation”

Fork and update (v0.6.5) of the original @modelcontextprotocol/server-puppeteer MCP server for browser automation using Puppeteer.

Unique: Wraps Puppeteer's ElementHandle operations as stateless MCP tools that re-query the DOM on each call, avoiding stale reference issues common in long-running automation scripts. Includes automatic visibility waiting before interaction.

vs others: More robust than direct Puppeteer ElementHandle usage for agent workflows because it handles element re-querying and visibility waiting transparently, reducing agent-side error handling complexity.

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 manipulation”

100-tool browser automation for AI agents via Chrome extension. Screenshots, DOM inspection, network capture, form filling, session recording, structured data extraction. npx crawlio-browser init auto-configures 14 MCP clients.

Unique: Offers real-time DOM manipulation capabilities that integrate seamlessly with the MCP framework for immediate feedback.

vs others: More interactive than traditional developer tools as it allows for live editing and immediate results.

via “dynamic dom manipulation”

We built AI Subroutines in rtrvr.ai. Record a browser task once, save it as a callable tool, replay it at: zero token cost, zero LLM inference delay, and zero mistakes.The subroutine itself is a deterministic script composed of discovered network calls hitting the site's backend as well as page

Unique: Offers a straightforward API for DOM manipulation that integrates seamlessly with existing web technologies without additional libraries.

vs others: Faster and more intuitive than jQuery or similar libraries for simple tasks due to direct access to native APIs.

via “dom-element-manipulation”

via “dom-element-interaction”