Puppeteer Debugger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUPPETEER_EXECUTABLE_PATH | No | The path to the Chrome or Chromium browser executable if it is not in a default location (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows or /usr/bin/google-chrome on Linux). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | 导航到指定 URL |
| get_console_errorsB | 获取 Console 异常和日志 |
| check_elementB | 检查元素状态（属性、样式、可见性等） |
| get_cache_statusB | 获取缓存状态（LocalStorage、SessionStorage、Cookies、IndexedDB） |
| get_performanceC | 获取性能数据（Performance Timeline、页面加载指标） |
| get_heap_snapshotB | 获取堆快照（建议先让用户选择是否导出 raw snapshot，以及导出方式：none/file/inline/both） |
| analyze_memoryC | 分析内存使用情况 |
| track_allocationsC | 跟踪对象分配 |
| take_screenshotA | 截图工具（辅助调试）。支持视口截图和全页截图。建议在使用前询问用户希望的输出方式：如果用户需要直接查看图片，使用 inline 模式返回 base64；如果用户需要保存图片文件，使用 file 或 auto 模式保存为文件。对于全页截图或大图片，强烈建议使用 file/auto 模式避免响应过大。 |
| get_lighthouseC | 获取 Lighthouse 性能报告（包括性能、可访问性、最佳实践、SEO 等指标） |
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 10 tools
Each tool targets a distinct debugging concern: memory, elements, cache, console, heap, performance, Lighthouse, navigation, screenshots, and allocations. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_memory, check_element, get_cache_status). No deviations or mixed conventions.
With 10 tools, the set is well-scoped for a debugging server. It covers essential debugging operations without being overwhelming or sparse.
The server covers major debugging areas: navigation, inspection, performance, memory, and console. Minor gaps like network request monitoring or DOM interaction are absent, but core debugging workflows are supported.