PixelPilot: Instructions file for GitHub Copilot

OpenCode UI/UX 2026 — MCP Server Setup

This document provides concrete configuration snippets for setting up Model Context Protocol (MCP) servers for Chrome DevTools and Lighthouse CLI. These configurations are essential for automating UI/UX audits and performance assessments within the OpenCode design system. Both tools are free and open source, ensuring broad accessibility and cost-effectiveness.

1. Chrome DevTools MCP Configuration

This configuration enables the uiux-audit-automation.md skill to interact with Chrome DevTools for automated accessibility (axe-core) scans and other UI/UX audits. The MCP server facilitates programmatic control over a headless Chrome instance, allowing for consistent and repeatable testing.

opencode.json Snippet

Add the following object to the servers array within your opencode.json file. Ensure the port is unique if you have other MCP servers running.

{
  "name": "chrome-devtools-mcp",
  "type": "devtools",
  "port": 9222, // Default Chrome DevTools port
  "args": [
    "--headless=new",
    "--disable-gpu",
    "--remote-debugging-port=9222",
    "--no-sandbox" // Required for some environments, use with caution
  ],
  "chromePath": "/usr/bin/google-chrome" // Adjust based on your Chrome installation path
}

Verification Steps

After adding the configuration and restarting your MCP client, you can verify the server is running and accessible using the /mcp list command:

/mcp list

You should see chrome-devtools-mcp listed among the active servers. You can also try to connect to localhost:9222 in your browser to confirm the headless Chrome instance is listening.

Troubleshooting Tips

• Chrome Path: Ensure chromePath points to the correct executable for your system. Common paths include /usr/bin/google-chrome, /usr/bin/chromium-browser, or /Applications/Google Chrome.app/Contents/MacOS/Google Chrome on macOS.
• Permissions: If you encounter permission errors, ensure the user running the MCP server has execute permissions for the Chrome executable. The --no-sandbox flag can resolve some issues in containerized environments but should be used judiciously due to security implications.
• Port Conflicts: If port 9222 is already in use, choose another available port and update the port and remote-debugging-port values accordingly.