Skip to content

Commit 0ecbd79

Browse files
Add WordPress debugging example to README
Added example for debugging a WordPress site using MCP.
1 parent 5c1ecf8 commit 0ecbd79

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -321,6 +321,21 @@ Your MCP client should open the browser and record a performance trace.
321321

322322
> [!NOTE]
323323
> The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.
324+
## Example: Debugging a WordPress Site Using MCP
325+
326+
This example demonstrates how `chrome-devtools-mcp` can be used to debug
327+
and analyze a locally hosted WordPress site using Chrome DevTools automation.
328+
329+
### Prerequisites
330+
- Local WordPress setup (XAMPP, LocalWP, Docker, etc.)
331+
- Google Chrome
332+
- Node.js installed
333+
334+
### Steps
335+
336+
1. Start Chrome with remote debugging enabled:
337+
```bash
338+
google-chrome --remote-debugging-port=9222
324339

325340
## Tools
326341

0 commit comments

Comments
 (0)