chrome-devtools-mcp list_console_messages includes optional stack traces
Introduced 2026-08-25 · score 0.97
HOW TO USE IT
When identifying where console errors originate, call `list_console_messages` with `includeStackTraces: true` to include available stack traces in the results. Frames are source-mapped and ignore-list-filtered.
{"name":"list_console_messages","arguments":{"includeStackTraces":true}}WHY THIS HELPS
Identify the source location of console errors while debugging a page.
BEFORE THIS CHANGE
The release note says the list output previously provided plain message text, requiring a `get_console_message` call for each message to obtain its source location.
REQUIREMENTS AND LIMITATIONS
- Version: 1.8.0
- includeStackTraces: Boolean; set true to include available stack traces. Increases response size; defaults to false. Stack traces appear as indented frames in text and as a pre-formatted `stackTrace` string in `structuredContent`.
- Prerequisite: Use a connected Chrome DevTools MCP server and select the page to inspect; this tool lists messages for the currently selected page since its last navigation.
- Stack traces are included only when available.
- `includeStackTraces` defaults to false and increases response size.
- Stack frames are source-mapped and ignore-list-filtered.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v1.8.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/2505
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/85c73a0abc85a2a4e8b7705955dddcede543ebae/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON