Labsco
MCP SERVER

Autoconsent MCP

by noisysocks ↗

Drive a real browser to inspect a site's cookie banner, search the DOM for just the parts that mention what you are looking for, and run a candidate Autoconsent rule against the live page.

Browser Automation, Control & Screenshots
Summary
The loop of writing a consent-banner rule, shortened.

Finding the accept button inside a page of minified markup is most of the work, and a whole-page dump is unreadable. Returning only the elements that contain what you asked for, then testing the rule against the live site, is the pair that matters.

What it is

A browser-automation MCP server built around one job: writing and testing Autoconsent rules. Alongside navigation, clicking and screenshots, it can search a page's HTML for elements that deeply contain a query, print one element in full, and execute an Autoconsent rule against a URL.

What you get
  • A real browser navigated to any URL
  • Screenshots of the whole page or one element, as an image or a base64 data URI
  • Clicks, select-box choices, and arbitrary JavaScript run in the page
  • HTML of only the elements that contain your search query, the rest elided with a placeholder
  • The full HTML of one element by CSS selector
  • An Autoconsent rule run against a URL and the outcome reported
  • Browser console output and captured screenshots exposed as resources
Requirements

Node.js 18 or higher and npm, with a local build step. The browser runs on your machine with your access, so it can reach local files and internal IP addresses — keep it pointed away from anything sensitive.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary