Toolshed

Two organizations shipped something called Toolshed within ten days of each other in February 2026, and both mean the same architectural move: one MCP server standing between coding agents and everything else.

Alistair Gray's first post on Stripe's Minions, dated 2026-02-09, describes Toolshed as a centralized platform hosting more than 400 MCP tools, giving the agents unified access to Stripe's internal systems without per-agent configuration. Minions were merging over 1,000 pull requests a week at that point. His follow-up on 2026-02-19 puts the count at roughly 500 tools and adds the detail that outweighs the number: each agent receives a curated subset matched to its task. Gray's stated reason is context overload, which degrades LLM performance. The hub is built to be partitioned before it is handed to an agent.

Cloudflare's Toolshed, announced 2026-02-12 in the same post as Markdown for Agents, gathers more than 400 MCP tools as a central platform for agent tooling. That post also records Cloudflare converting HTML to Markdown at the edge for agents that send the header Accept: text/markdown, which Claude Code already does.

The common bet is that the binding constraint in agent engineering is context capacity. Stripe's version is internal plumbing for a codebase of hundreds of millions of lines, mostly Ruby; Cloudflare's is a platform offered outward. Neither account explains how a curated subset gets selected for a given task, which is where the whole design rests.