Browser MCP Resource Guard

Goal

Reduce CPU, memory, battery, and fan impact from browser automation MCP tools without breaking active work. Treat cleanup as a guarded operation: inspect first, report clearly, and only kill processes when it is safe or explicitly requested.

Decision Rules

• Prefer not using browser MCP when static checks, local files, tests, builds, or ordinary HTTP requests answer the task.
• Use Chrome DevTools MCP when the task needs live browser state, console messages, network requests, DOM snapshots, screenshots, viewport checks, or real interactions.
• Use browser MCP in focused batches: open the page, collect needed evidence, close or stop related local services when finished.
• Avoid repeated screenshots, repeated new tabs, performance traces, heap snapshots, and attaching to a Chrome profile with many tabs unless the task requires them.
• After browser MCP use, run a read-only process check when the session was long, multiple pages/tools were used, or the user mentions energy/resource problems.

Read-Only Check

Run the bundled report script from the skill directory: