Running MCP across a team without making a mess
One engineer with five servers is fine. Twenty engineers with their own five each is an audit finding waiting to happen — and it arrives on the day somebody leaves.
MCP is trivial for one person and becomes a governance problem at about the fifth install. This is what changes: keys per machine rather than per person, installs owned by an account rather than a laptop, two ceilings that do different jobs, an audit trail that answers who approved what, and the two mistakes teams make first.