Daily AI Builder Brief - May 5, 2026

Executive Summary

Claude Code v2.1.128 lands with plugin .zip archive support and cleaner MCP reconnect behavior.
/mcp now shows per-server tool counts and flags servers that connected with 0 tools, so silent failures stop hiding.
Console (API key) auth gains --channels support, closing a gap that previously needed OAuth.
Model picker collapses duplicate Opus 4.7 entries; current Opus now displays simply as "Opus."
EnterWorktree now branches from local HEAD, preserving unpushed commits across worktree spawns.
Anthropic forms a Claude-focused enterprise services JV with Blackstone, Hellman & Friedman, and Goldman Sachs aimed at mid-market deployments.
Jama Software ships the first engineering-management MCP server, opening Spec Driven Development to requirements-graph workflows.
No new MCP spec activity since the April 8 maintainer team expansion; movement is at the integration layer.

Claude Code

v2.1.128 ships (May 4)

Plugin loader now accepts .zip archives via --plugin-dir, friendlier for download links and registries. /mcp reports per-server tool counts and surfaces servers that connect with 0 tools. workspace is now a reserved MCP server name. On reconnect, tool re-announcements get summarized by server prefix instead of flooding the conversation. Subprocesses no longer inherit OTEL_* env vars, which stops telemetry leaking into spawned tools. Bare /color randomizes session color. Roughly 35 bug fixes across focus mode, drag-and-drop, autocompaction, and parallel shell execution. changelog

Anthropic

Enterprise AI services JV with Blackstone, H&F, Goldman (May 4)

A new joint venture pairs Anthropic Applied AI engineers with capital and operations from three financial firms to deliver custom Claude implementations to mid-sized companies. Company name not disclosed. Builders selling Claude tooling should watch for procurement patterns flowing through this entity into the mid-market. announcement

MCP Ecosystem

Jama Connect MCP server (May 4)

Jama released what it bills as the first MCP server for engineering management. The pitch is Spec Driven Development: agents read and write against the requirements graph, giving Claude direct hooks into hardware and regulated-systems workflows. First-of-kind in a vertical that's been MCP-light. release

Broader AI

Nothing today.

What This Means For Builders

If you ship plugins, move to .zip distribution. It's a cleaner artifact for registries and update flows than raw directories.
Audit your MCP server list with the new /mcp tool-count view. Zero-tool servers were silent failures; now they're visible.
The Anthropic JV signals mid-market is the next channel. If your product sits next to Claude, expect more RFPs shaped by that buyer profile.
Spec Driven Development via MCP is now proven in regulated engineering. Worth copying for anything graph-shaped (compliance, finance ops, infra).