Skip to content

Add WordPress debugging example to README #747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
VaibhavChhillar wants to merge 1 commit into from
Closed

Add WordPress debugging example to README #747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading