#mcp

Every team that adopted MCP hit the same wall by spring: forty tools in the context, a model that picks the wrong one, and a bill that grew with every server you added. Skills, the folder-of-markdown pattern that spread through coding agents this year, fix a different problem than MCP does. Knowing which is which decides whether your agent gets better or just bigger.

A single GitHub issue was enough to make a coding agent leak a private repo through the official MCP server. The Git MCP server fell to path traversal from a prompt alone in January. None of these were model failures. They were the same mistake we made with SQL in 2004: letting data and instructions travel on the same wire.