navigateLABSCO 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 — git clone https://github.com/noisysocks/autoconsent-mcp.git
USE CASES
01
Finding the accept button in a page of minified markup
Load the site, search the DOM for the wording you expect, and get back only the elements that contain it — then print the promising one in full.
02
Checking whether the rule you wrote actually fires
Run the candidate rule against the real URL and see the result, rather than reasoning about the selector.
03
Seeing what the banner looks like before and after
Capture the page as an image, apply the rule, and capture it again.
04
Poking at a banner that only appears once you interact
Click through to the state where the banner exists, then run JavaScript in the page to inspect it.
8 tools
Listed in project docs. Your client may show a different list.
screenshotclickselectevaluatesearch_htmlprint_elementtest_ruleBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- node on PATH
- Node.js
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/noisysocks/autoconsent-mcp.git
cd autoconsent-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"autoconsent-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_AUTOCONSENT_MCP>/dist/index.js"
]
}
}
}
