Summary
CoPaw merged PR #4849 adding SharedMCPPool, letting multiple agents reuse MCP server connections instead of each agent managing its own isolated servers. The change targets performance and scaling for multi-agent deployments.
What changed
CoPaw added a SharedMCPPool for MCP server reuse across agents.
Why it matters
As multi-agent workflows become common, each agent opening separate tool-server connections can add startup latency, resource pressure, and reliability problems. Shared MCP pooling turns tool access into shared infrastructure rather than per-agent plumbing.
Evidence excerpt
Agents Radar lists PR #4849 as adding SharedMCPPool to reuse MCP servers across agents, describing it as a performance optimization.