# Job sessions stop hauling browser tooling they never use

Every scheduled job (the health check, the commitment scan, and friends) runs as a small one-shot Claude session. Until now, every one of those sessions booted with the project's FULL set of MCP servers attached — the browser-automation server, remote connectors that need interactive login, all of it — even though the shipped jobs only ever use bash and curl. That's wasted startup time on every single run (the health check spawns every five minutes), extra standing processes on the box, and a known hazard: a remote MCP server that wants an interactive login can stall a headless session for minutes (this exact stall already bit the mentor loop once, and that fix is what we reuse here).

A job can now declare `mcpAccess: none` in its definition, which makes its session spawn with zero project MCP servers — the same proven no-MCP spawn flag the mentor loop already uses. Fourteen shipped utility jobs declare it; jobs that don't declare anything behave exactly as before, and any job that genuinely needs MCP just leaves the field off (or says `project`). The orchestration jobs that drive other sessions were deliberately left unchanged this round. A typo'd value never silently changes behavior: the installer treats it as undeclared, and a hand-written bad manifest fails loudly at validation.
