MCP Browser Debugger
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 | Navega para uma URL específica e carrega a página completamente |
| get_domC | Extrai o HTML completo do DOM atual da página |
| get_elementC | Inspeciona um elemento específico usando seletor CSS |
| execute_jsC | Executa código JavaScript arbitrário no contexto da página |
| screenshotB | Captura uma screenshot da página ou de um elemento específico |
| get_console_logsC | Recupera todos os logs do console capturados desde a última navegação |
| get_network_activityC | Recupera todas as requisições de rede capturadas |
| get_page_sourceB | Extrai todo o código fonte da página incluindo scripts, styles e recursos |
| query_selector_allC | Busca todos os elementos que correspondem ao seletor CSS |
| get_page_infoB | Obtém informações gerais sobre a página atual |
| click_elementC | Clica em um elemento da página |
| type_textC | Digita texto em um campo de input |
| get_local_storageB | Obtém todos os dados do localStorage |
| get_cookiesB | Obtém todos os cookies da página atual |
| evaluate_xpathC | Avalia uma expressão XPath e retorna os elementos correspondentes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, click_element is for clicking, evaluate_xpath for XPath evaluation, get_dom for DOM extraction, and navigate for page navigation—each targets a specific browser debugging action without overlap.
All tool names follow a consistent verb_noun pattern in snake_case, such as click_element, get_cookies, and navigate. This predictability makes it easy for agents to understand and select the right tool based on its naming convention.
With 15 tools, the server is well-scoped for browser debugging, covering essential actions like navigation, DOM inspection, JavaScript execution, and data retrieval. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides complete coverage for browser debugging, including navigation, element interaction, data extraction, and monitoring. There are no obvious gaps; agents can handle full debugging workflows from page loading to inspection and interaction.