Debugging and verifying MCP servers using the MCP Inspector UI with Playwright automation

Rule Name: mcp-inspector
Description: Debugging and verifying MCP servers via the MCP Inspector UI. This rule uses Playwright for UI automation, iTerm for server management, and Claude Code for log inspection.

**Note:** Replace placeholders with your specific values:
- `[MCP_SERVER_NAME]` - Your MCP server name
- `[WORKSPACE_PATH]` - Absolute path to your project
- `[TEST_CREDENTIALS]` - Any test credentials needed
- `[CONFIG_FILE]` - Your configuration file path
- `[LOG_FILE]` - Your log file path

To read the log, use `tail -n 100 /path/to/logfile.log`

DO NOT RUN BLOCKING TERMINAL COMMANDS VIA YOUR TERMINAL TOOL. INSTEAD USE Terminal app via AppleScript.
Blocking operations include: 
- `node dist/index.js`
- `npm run dev`
- `npm start`

This is ok:
Grab the last X lines: `tail -n 100 server.log`

Run `npm run build` to verify build.

Check iTerm log when the MCP Inspector fails, as it might show errors from our service.