Every processed story in chronological order, with the newest coverage first. Filter by tag, source, or score to drill in.
The post provides production evidence that the widely cited ~15-tool MCP limit is a proxy for ambiguity rather than a hard count ceiling, and demonstrates that naming grammar, description-level routing instructions, and selection-focused evals can keep a 27-tool server accurate.
The post highlights a structural gap in the MCP ecosystem — the long tail of internal and niche SaaS tools that will never ship a dedicated server — and describes a browser-native injection pattern as a lightweight alternative to both vision-based agent loops and full MCP server deployments.