I checked the expectation that an MCP server makes an agent better over 240 runs. The post compares scores, unsafe actions, tokens, and read-only designs per server, and suggests which server fits which situation.
Native support does not mean the workaround has to go. The documented pitfalls, plus 80 runs from the July extension study, decide what to keep and what to fix.
The two AGENTS.md migration workarounds (import, symlink) were measured on Kubernetes incident-response tasks: no penalty in speed or context-load tokens; deltas moved with the symlink control, marking them as run variance.
Putting nine agents through ten Kubernetes incident scenarios under identical conditions surfaced two things: the Efficient tier beat Flagship outright, and each brand has a clearly different operational personality.