bld-mcp-settingslisted

# bld-mcp-settings — on-demand or always-on BLD ships three MCP servers and runs them **on demand** by default: spawn, fire one batch of queries, kill. This skill switches them to **always-on** instead, by writing them into `.mcp.json` so Claude Code connects them at startup and keeps them for the whole session. Two settings, one file. Nothing else changes. | Setting | What it means | How the servers run | |---|---|---| | **off** (default) | No `.mcp.json`, or none of BLD's servers in it | `/bld-runtime-activate-mcps` spawns one, queries it, kills it | | **on** | Named servers written into `.mcp.json` | Claude Code starts them at launch and holds them open | ## Say this before turning anything on The default is off **on purpose**, and the user should hear why once before changing it. Not as discouragement, as information: > **Always-on means the server sees your session, not just your query.** On > demand, a server is alive for the few seconds of one batch and only ever > receives the specific calls sent to it. Always-on, it is connected the whole > time you work. That is genuinely more convenient, and it is a real change in > what a third-party tool can observe. Then let them decide. **Do not refuse, and do not repeat the warning.** ## The one that is not like the others `jcodemunch` and `shadcn` are read-only lookups. **`context-mode` is not.** Its `ctx_execute` runs real shell commands using whatever CLIs are already logged in (`gh`, `aws`, `vercel`). On demand, t