Question in the title. This is mostly for my non-dangerously-skip-permissipns brethren. I know I can avoid all of these troubles by using dev containers or docker and bypassing all permission prompts. However, I’m cautious by nature. I’d rather learn the toolset than throw the yolo flag on and miss the opportunity to learn. I tend to agree that CLI tooling is much better on the whole, compared to MCP. Especially when factoring in baseline token usage for even thinking about loading MCP. I also prefer to write bash wrappers around anything that’s a common and deterministic flow. But I keep running up against this frustration. What’s the comparable pattern using a CLI when you want to pass data to the script/cli? With MCP tool parameters passing data is native and calling the tools is easily whitelisted in settings.json. Are you writing approve hooks for those CLI calls or something? Or asking Claude to write to file and pipe that to the CLI? I’m know I’m probably missing a trick here so I’d love to hear from you what you’re doing. submitted by /u/jetsy214
Originally posted by u/jetsy214 on r/ClaudeCode