74 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
OpenAI Adopted Anthropic's Agent Skills Format in 48 Hours — What That Means for Your Deploy Runbooks
OpenAI adopted Anthropic's Agent Skills packaging format within 48 hours of its release, not just its MCP protocol. Here's what that convergence changes about writing a portable runbook Skill instead of a bespoke one.
Vercel Shipped an Official MCP Server. Here's Every Tool It Refuses to Give Your Agent
Vercel's official MCP server took a year to gain its first write tool — and it still can't touch an existing project's env vars, domains, or a rollback. A tool-by-tool audit of the agent-ops bar the market leader actually set.
The AI Rollback Paradox: 81% of the Best-Governed Teams Pulled Their Agents Anyway
Sinch's 2026 survey found 74% of enterprises rolled back a live AI agent — and the best-governed teams rolled back the most, at 81%. Here's what that means for building rollback into an MCP deploy surface as a cheap default instead of another approval gate.
Your Deploy Agent's Sandbox Will Die Mid-Rollout — Here's How Its MCP Server Should Survive That
MCP's July 2026 spec update made the protocol stateless — which means the burden of surviving a crashed sandbox now falls entirely on the MCP server. Here's the Postgres checkpoint design, borrowed from LangGraph, that a deploy-from-chat PaaS needs to make a multi-step rollout outlive the agent that started it.
Designing upgrade_cluster: An MCP Tool Contract for Fleet-Wide Kubernetes Node Upgrades
A deploy/rollback MCP tool that goes wrong costs a bad release. An upgrade_cluster tool that goes wrong can leave a fleet straddling a Kubernetes version-skew boundary mid-drain. Here's a concrete tool contract — plan mode, per-node health gates, and a hard stop — for handing an agent that authority safely.
The Rollback Floor: Designing a Deploy-From-Chat MCP Server That Can't Roll Back Too Far
A dashboard's rollback button only ever offers 'go back one.' An MCP tool wrapping the same API can't assume that restraint — here's a concrete tool contract, server-side floor, and audit schema that stop an agent from rolling back past the last known-good release.
MCP's '10,000 Connections at Sub-50ms' Claim Is True — and Doesn't Mean What You Think
The 2026 benchmark headline about MCP servers handling 10,000 connections at sub-50ms is technically true and mostly beside the point. Here's what a production deploy-from-chat MCP server actually needs when a fleet of agents, not one chat session, is calling it.
MCP's Tasks Extension Is Built for Work That Outlives a Single HTTP Request — Exactly the Shape of a Deploy
MCP's July 2026 spec ships a Tasks extension so a deploy tool call can outlive a single HTTP request — here's how tasks/get polling beats the hand-rolled deploy_status workaround every deploy-from-chat integration had to invent before it.
Wassette Runs MCP Tools as WebAssembly, Not Containers: What That Actually Buys a Self-Hosted Fleet
Microsoft's Wassette runs MCP tools as WebAssembly Components with deny-by-default WASI permissions instead of a container or a Firecracker microVM. Here's what the microsecond instantiation and policy.yaml grants actually buy a self-hosted fleet — and the GPU access, fork(), and resource-quota gaps that still mean a heavier sandbox for everything else.