266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
MCP’s Ecosystem Is Big Enough to Be an Attack Surface: Scope a Deploy-from-Chat Server
A practical permission, approval, and audit design for an MCP deploy server that keeps untrusted tool context from becoming a production action.
Railway’s ChatGPT and Grok Plugins Show Why Deploy-From-Chat Needs an Open Control Plane
Railway’s ChatGPT and Grok plugins point to a host-neutral control-plane design for safely deploying and operating a PaaS from any chat client.
Your MCP Server Lost Its Confirmation Prompt on July 28: Rebuilding the Delete Gate on input_required
The 2026-07-28 MCP spec deleted server-initiated requests, and with them the only way a destructive tool could stop and ask a human. Here is the replacement on the wire: a delete_service gate built on resultType input_required, the signed requestState ticket that survives a round-robin load balancer, and the once-only guarantee the protocol makes your problem.
AWS DevOps Agent Goes GA But Still Can't Deploy the Fix: The Diagnose-Not-Act Line
AWS DevOps Agent reached GA finding root causes in minutes — but it still refuses to execute the fix. Why every enterprise agentic-ops vendor stops at diagnosis, and the five pieces of platform machinery needed before an AI agent can safely deploy the rollback itself.
Coolify v4 Shipped an MCP Server. Dokploy Didn't. The Self-Hosted PaaS Race Just Split in Two
Coolify's v4.x releases made a native MCP server its headline differentiator while Dokploy stayed deliberately minimal. A side-by-side comparison of both platforms — idle RAM, install, MCP surface — and why agent-operability's real cost is API discipline, not footprint.
Sprites Speak MCP: When the Agent Sandbox Becomes a Tool the Agent Calls Itself
Fly.io's Sprites now expose their full lifecycle over MCP, so agents provision disposable machines from inside their own loop. Here is the six-tool sandbox contract — create, exec, checkpoint, restore, destroy, list — and the quotas, TTLs, and per-tenant budgets a self-hosted platform needs before the agent becomes the capacity planner.
MCP Just Passed 22,000 Servers. Almost None of Them Can Deploy Anything.
MCP has 22,000+ servers and 97M monthly downloads, but almost all of them are read-only lookups. Here's what idempotent deploys, rollback, and audit logging actually require from the ones that aren't.
MCP's Stateless Core Just Shipped: What a Deploy-From-Chat MCP Server Gets to Delete
MCP's biggest spec rewrite since launch went final on July 28, 2026, killing the session model a deploy/rollback MCP server used to need. A concrete before/after of what infrastructure gets deleted and what still has to run.
MCP's Stateless Core Just Shipped: What a Deploy-From-Chat MCP Server Gets to Delete
MCP dropped protocol-level sessions on July 28, 2026 — deleting the sticky routing and shared session store a self-hosted deploy/rollback MCP server used to need, and adding a formal lifecycle policy worth pinning to.