When you should not install MCP

If one command is enough, do not wire a server. MCP has process, permission, and context cost.

A stable CLI and a one-shot job belong to git, rg, or a repo script. Another MCP layer is just another config that will rot.

Too many tools burn context. A dozen rarely used servers crowd out the code you meant to edit. Install one you can verify.

Do not hand production secrets, customer data, or systems you do not own to an unknown process. A listing here is public metadata, not an audit.

Install when you need session state, a permission fence, or repeated access to the same system. See MCP vs CLI and pick an entry that already has install metadata.