gridctl

For a long time, my definition of a successful software release was pretty simple: the tests passed, the binaries built, and the checksums matched. Ship it! That still sounds reasonable, but there is a gap hiding between we built some bytes and users downloaded the bytes we intended to publish.

I’ve written many nearly identical Python Dockerfiles. Pick a base image, install dependencies, add a non-root user, find the right console script, and do it again when the next MCP server shows up. That’s a lot of container housekeeping for a tool that might only tell an agent what time it is.

On July 28th, the MCP maintainers shipped the 2026-07-28 revision. No more initialize. No more initialized. No more Mcp-Session-Id. David Soria Parra called it “MCP’s most important release since remote MCP first launched over a year ago,” and I couldn’t agree more. In the weeks leading up to the release, I had the opportunity to have Angie Jones on the podcast to talk through some of the changes, community, and excitement on Episode 80 of The Cloud Gambit Podcast - (have a listen!)