From 1ab5894bfd08130efdfd2c41af48c338a1b3b14b Mon Sep 17 00:00:00 2001 From: Richard Michael Date: Thu, 11 Dec 2025 19:29:28 -0800 Subject: [PATCH 1/4] Typo --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 7fc62eac..83b5dd96 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -7,7 +7,7 @@ - When configuring your MCP client, try using the `--yes` argument to `npx` to auto-accept installation prompt. - Find a specific error in the output of the `chrome-devtools-mcp` server. - Usually, if you client is an IDE, logs would be in the Output pane. + Usually, if your client is an IDE, logs would be in the Output pane. ## Specific problems From 374be37df14f1eb5c9616b6182b4316986fa9a4b Mon Sep 17 00:00:00 2001 From: Richard Michael Date: Thu, 11 Dec 2025 19:29:43 -0800 Subject: [PATCH 2/4] Add log file debugging instructions --- docs/troubleshooting.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 83b5dd96..392eddf3 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -9,6 +9,33 @@ - Find a specific error in the output of the `chrome-devtools-mcp` server. Usually, if your client is an IDE, logs would be in the Output pane. +## Debugging + +Start the MCP server with debugging enabled and a log file: + +- `DEBUG=mcp:log npx chrome-devtools-mcp@latest --log-file=/path/to/chrome-devtools-mcp.log` + +Using `.mcp.json` to debug while using a client: + +```json +{ + "mcpServers": { + "chrome-devtools": { + "type": "stdio", + "command": "npx", + "args": [ + "chrome-devtools-mcp@latest", + "--log-file", + "/path/to/chrome-devtools-mcp.log" + ], + "env": { + "DEBUG": "mcp:log" + } + } + } +} +``` + ## Specific problems ### `Error [ERR_MODULE_NOT_FOUND]: Cannot find module ...` From e43dd8212bf16c73ac95ada3d75eb5603446a8f6 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Fri, 12 Dec 2025 10:32:45 +0100 Subject: [PATCH 3/4] Update docs/troubleshooting.md --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 392eddf3..6547fdfe 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -29,7 +29,7 @@ Using `.mcp.json` to debug while using a client: "/path/to/chrome-devtools-mcp.log" ], "env": { - "DEBUG": "mcp:log" + "DEBUG": "*" } } } From e9bc59de1917ad088d61df3992be295d841a6d8c Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Fri, 12 Dec 2025 10:33:37 +0100 Subject: [PATCH 4/4] Apply suggestion from @OrKoN --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 6547fdfe..6a7e36bc 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -13,7 +13,7 @@ Start the MCP server with debugging enabled and a log file: -- `DEBUG=mcp:log npx chrome-devtools-mcp@latest --log-file=/path/to/chrome-devtools-mcp.log` +- `DEBUG=* npx chrome-devtools-mcp@latest --log-file=/path/to/chrome-devtools-mcp.log` Using `.mcp.json` to debug while using a client: