Blog
Insights, analysis, and updates from the AI agent economy. Browse by tag · Browse the archive.
MCP Is the Transition Technology: What Infrastructure-First Enterprise AI Means for Your Deploy API
Enterprises stopped asking which model to pilot and started standardizing how agents reach production systems, with MCP as the emerging standard shape. Here is what that shift validates for a self-hosted deploy API — and which enterprise demands to adopt or skip on day one.
MCP Went Stateless: What the 2026-07-28 Spec Means for Long-Running Deploy Tools
MCP revision 2026-07-28 drops sessions, handshakes, and server-initiated requests. A migration map for deploy-from-chat servers whose minute-long tools must rebuild on Tasks, multi-round-trip confirmations, and an explicit task store.
Five MCP Launches in Five Days — and the Deploy Surface Still Missing
Between September 14 and 18, Rubrik, Algolia, Google, ReleasePad, and the UN all shipped MCP servers — each with governance baked into the protocol layer. Deploy infrastructure is the surface still missing, and third-party servers are already defining it.
454 MCP Servers Catalogued and Quality-Scored Daily: Finding a Production-Grade Server in a Flood of Demos
A daily automated scan catalogues 455 MCP servers and scores them on hygiene — average 16 out of 100. What the data reveals about supply, churn, and how to vet servers before your agents call them.
MCP Just Got Its Biggest Update Ever: What Stateless Servers Mean for Self-Hosting Deploy-from-Chat
The 2026-07-28 MCP spec killed sessions, sticky routing, and handshake affinity — September coverage calls it the biggest update since launch. For self-hosters, that means an infrastructure MCP server is now an ordinary HTTP service behind the same load balancer as everything else.
Your MCP Deploy Tool's dry_run Flag Is a Suggestion, Not a Lock
MCP tool annotations like readOnlyHint are advisory hints for the client, not enforcement — nothing in the protocol stops a caller from overriding dry_run, tenant_id, or target_environment. A three-line server-side pattern (derive from the session, reject client values, log the attempt) and where host-authority receipts belong.
The Managed Control-Plane Tax: Coolify $5 vs Dokploy $4.50/Server vs Deploynix $12 — and the Server Count Where the Meter Comes Back
Dokploy's $4.50 managed panel wins at one server, Coolify's $5 base wins at two through four, and Deploynix's flat $12 wins at five — a server-by-server fee accounting that names the count where each panel costs more than the Hetzner box it manages.
We're Leaving Kubernetes: What the Exit Posts Get Right About Small-Team Overhead, and What a PaaS Layer Answers
A fair accounting of the recurring 'we're leaving Kubernetes' posts: which small-team complaints survive scrutiny with real numbers, why most exits just rent someone else's Kubernetes-shaped API, and what a git-push PaaS layer answers.
Laravel MCP 1.0 Ships: Your Laravel App Is Now an Agent Tool — What Changes on the Deploy Surface
Laravel MCP 1.0 adopts the stateless MCP 2026-07-28 spec with searchable tool catalogs, cache hints, and mandatory OAuth PKCE — plus header validation that 400s old clients. Here is the upgrade checklist and what per-app MCP servers mean for anyone operating Laravel apps.
Subscribe
New posts land in your reader as soon as they publish. Pick a format — all three carry the same posts.
Current feeds keep roughly two days of posts so daily polling does not miss a burst. Older entries stay reachable from the feed's next-page link in readers that follow it, or from the blog archive.
Following one topic instead? Browse tags