Commit 15ff9dc
authored
feat(mcp): disable Playwright MCP by default (#77)
## Summary
Flip Playwright MCP's default \`enabled\` from \`true\` to \`false\`.
Browser tools become opt-in — neither the main agent nor the
browser-pilot crew sees \`browser_navigate\`, \`browser_click\`,
\`browser_screenshot\`, etc. until the user explicitly enables the
Playwright server from the MCP settings UI.
## Why
The main agent shouldn't reach for browser tools unprompted. The intent
is:
- Browser work → \`use_crew(\"browser-pilot\", ...)\` deliberately
- Main agent stays focused on orchestration
When the user enables Playwright via the UI, both the main agent and
browser-pilot get the tools back simultaneously (current architecture is
single shared MCP server, no per-crew scoping yet — that's a separate
larger change tracked elsewhere).
## Affected behaviour
- **Fresh installs**: no browser tools by default. User clicks Enable in
MCP settings → tools restored to both the main agent and browser-pilot.
- **Existing users**: their \`mcp.json\` already has \`enabled: true\`
from when they first installed; this PR doesn't migrate that. They keep
browser tools unless they manually disable.
## Test plan
- [x] \`npx tsc --noEmit\` clean
- [ ] Fresh install: confirm Playwright doesn't show in the agent's tool
list
- [ ] Enable Playwright from MCP settings: confirm \`browser_*\` tools
reappear, browser-pilot can run
- [ ] Disable again: confirm both surfaces lose the tools1 file changed
Lines changed: 7 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
260 | 260 | | |
261 | 261 | | |
262 | 262 | | |
263 | | - | |
| 263 | + | |
264 | 264 | | |
265 | 265 | | |
266 | 266 | | |
| |||
277 | 277 | | |
278 | 278 | | |
279 | 279 | | |
280 | | - | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
281 | 286 | | |
282 | 287 | | |
283 | 288 | | |
| |||
0 commit comments