Autoconsent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateC | Navigate to any URL in the browser |
| reloadB | Reload the current page |
| screenshotC | Capture screenshots of the entire page or specific elements |
| clickC | Click elements on the page |
| selectC | Select an element with SELECT tag |
| evaluateC | Execute JavaScript in the browser console |
| search_htmlA | 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_elementB | Outputs the full HTML of the given element |
| test_ruleC | Tests the given Autoconsent rule on the given URL |
| reset_browser_dataC | Reset browser data including cookies, cache, localStorage, and sessionStorage |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 10 tools
Most tools have distinct purposes, but 'evaluate' and 'test_rule' could be confused as both involve executing code or rules in the browser context. The other tools like 'click', 'navigate', and 'screenshot' are clearly differentiated by their specific actions on web pages.
The naming is mixed with some tools using verb_noun patterns like 'print_element' and 'search_html', while others are single verbs like 'click' and 'reload'. There is no consistent convention across all tools, but the names are generally readable and descriptive of their functions.
With 10 tools, the count is well-scoped for a browser automation and testing server. Each tool appears to serve a specific purpose in interacting with web pages, such as navigation, element manipulation, and data resetting, making the set comprehensive without being overwhelming.
The toolset covers core browser automation tasks like navigation, interaction, and inspection, with notable tools for Autoconsent-specific testing. A minor gap is the lack of tools for handling pop-ups or alerts, which are common in consent management scenarios, but agents can work around this using existing tools like 'click' or 'evaluate'.