From 0ecbd795724b42f1d34b148d0eca3292e8ff83a8 Mon Sep 17 00:00:00 2001
From: Vaibhav Chhillar <131567808+VaibhavChhillar@users.noreply.github.com>
Date: Fri, 9 Jan 2026 18:05:47 +0530
Subject: [PATCH] Add WordPress debugging example to README

Added example for debugging a WordPress site using MCP.
---
 README.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/README.md b/README.md
index 437233389..abce70459 100644
--- a/README.md
+++ b/README.md
@@ -321,6 +321,21 @@ Your MCP client should open the browser and record a performance trace.
 
 > [!NOTE]  
 > 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.
+## Example: Debugging a WordPress Site Using MCP
+
+This example demonstrates how `chrome-devtools-mcp` can be used to debug
+and analyze a locally hosted WordPress site using Chrome DevTools automation.
+
+### Prerequisites
+- Local WordPress setup (XAMPP, LocalWP, Docker, etc.)
+- Google Chrome
+- Node.js installed
+
+### Steps
+
+1. Start Chrome with remote debugging enabled:
+```bash
+google-chrome --remote-debugging-port=9222
 
 ## Tools