A Model Context Protocol server that provides browser automation capabilities specifically designed for creating and testing Autoconsent rules. This
Autoconsent MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol server that provides browser automation capabilities specifically designed for creating and testing Autoconsent rules. This server enables LLMs to interact with web pages, inspect consent management platforms.
Once Autoconsent MCP is connected, these are the calls the assistant has available:
navigate — Navigate to any URL in the browserInputs — - url (string, required): URL to navigate toscreenshot — Capture screenshots of the entire page or specific elementsclick — Click elements on the pageInput — selector (string): CSS selector for element to clickselect — Select an element with SELECT tagevaluate — Execute JavaScript in the browser consolesearch_html — Outputs the HTML of elements that deeply contain the given search query. Elements that don't contain the given query are omitted using a [...]print_element — Outputs the full HTML of the given elementtest_rule — Tests the given Autoconsent rule on the given URLTools — The Tools tool exposed by this serverResources — 1. Console Logs (console://logs) - Browser console output in text format - Includes all console messages from the browserThe server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Autoconsent MCP's toolset — navigate, Inputs, screenshot and 11 more — is a fair guide to whether it matches your workflow. It is maintained by noisysocks; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| navigate | Navigate to any URL in the browser |
| Inputs | - url (string, required): URL to navigate to |
| screenshot | Capture screenshots of the entire page or specific elements |
| click | Click elements on the page |
| Input | selector (string): CSS selector for element to click |
| select | Select an element with SELECT tag |
| evaluate | Execute JavaScript in the browser console |
| search_html | Outputs the HTML of elements that deeply contain the given search query. Elements that don't contain the given query are omitted using a [...] placeholder. |
| print_element | Outputs the full HTML of the given element |
| test_rule | Tests the given Autoconsent rule on the given URL |
| Tools | The Tools tool exposed by this server. |
| Resources | 1. **Console Logs** (console://logs) - Browser console output in text format - Includes all console messages from the browser |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | The Setup tool exposed by this server. |
{
"mcpServers": {
"autoconsent": {
"command": "npx",
"args": ["-y", "npm"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.