Agent and MCP Guide
This inventory is projected from the checked-in MCP configuration. Repository guidance defines how each server may be used; user-level tools are outside this project contract.
| Server | Command | Arguments | Scope | Surfaces |
|---|---|---|---|---|
| brave-devtools | node | scripts/mcp/brave-devtools.mjs | local-browser-debugging | client, admin, docs, storybook |
Safety boundary
- Green Goods browser proof is Brave-only. Do not use Google Chrome, Chrome for Testing, Chromium, or Edge as a fallback.
- The wrapper calls the upstream chrome-devtools-mcp package because that is the protocol package name; the browser executable must still be Brave.
- This isolated DevTools MCP server is public clean-room evidence only; it is not authenticated local QA.
- Use the authenticated Brave extension or visible-desktop path for admin, wallet, passkey, installed-PWA, and profile-dependent proof.
- Do not expose secrets, wallet state, passkeys, local storage, private garden data, telemetry identifiers, or hidden admin actions in prompts or reports.