74 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
MCP Goes Stateless on July 28: Why Model Context Protocol Servers Can Finally Run Behind a Plain Kubernetes Load Balancer
MCP's July 28, 2026 spec removes Mcp-Session-Id and the initialize handshake, so any request can land on any server instance — here's the before/after Kubernetes architecture and what it unlocks for an MCP server with deploy authority.
WebMCP Lets a Web Page Register Its Own AI Tools. Does a Deploy Dashboard Need One?
Chrome's new WebMCP API lets a web page register its own AI-callable tools, but a deploy dashboard already has a REST/GraphQL API and an MCP server. Here's the actual capability delta, and why it's not worth building yet.
A2A Turns One and Hits v1.0: What a Standard Agent-to-Agent Handshake Actually Buys a Deploy-From-Chat Pipeline
A2A hit v1.0 and 150+ organizations in its first year under the Linux Foundation. Here's a worked example of what its signed Agent Cards and task-approval states actually change for a deploy pipeline where one agent requests a rollback and another approves it — and whether a self-hosted PaaS's MCP server needs to speak it yet.
Giant Swarm's AI Agent Platform Proves Cluster API Scales — But Not Every Layer It Runs
Giant Swarm's production numbers — 2.8x lower cost per agent run, 500 parallel agents — validate Cluster API and GitOps as an AI-agent substrate. But its Backstage-centric IDP layer is a $300K-$700K/year commitment a simpler git-push control-plane API doesn't need.
Sealos and the Rise of Prompt-to-Deploy AI-Native Clouds: What 'Deploy Anything With a Prompt' Gets Right That a Git-Push PaaS Still Doesn't
Sealos pitches 'deploy anything with a prompt' as a new AI-native category, but its own architecture shows agent skills calling the same Kubernetes CRDs the dashboard already used. Here's the actual dividing line between a real AI-native platform and a chat UI bolted onto an existing API.
The AI Sandbox Market Just Got a Hyperscaler Problem
Five hyperscalers shipped agent-execution sandboxes within seven months. Here's what each one actually does, how it's squeezing E2B, Daytona, and Modal on price, and why the entry itself makes the case for running agent code on the same fleet that already deploys your app.
MCP Gives Agents Tools. Agent Skills Gives Them Runbooks.
A folder with a SKILL.md file can hold an entire deploy-troubleshooting runbook and cost an agent almost nothing until it's actually needed. Here's the token math on why that beats stuffing the same runbook into an MCP tool description — and what a deploy-from-chat MCP server should borrow from it.
Claude Code's Agents Now Push and Open PRs Unattended — Where Should Your Deploy Trigger Actually Bind?
Claude Code v2.1.198 shipped background agents that commit, push, and open a draft PR with no human in the loop. Here's the concrete trigger-point table for where a deploy pipeline should actually bind when the pusher might be an agent, plus the four-item audit checklist a self-hosted deploy-from-chat MCP server needs first.
Claude Code's Dynamic Workflows Cap Concurrency at 16, Not Hundreds: What a Real Subagent Burst Does to a Deploy MCP Server
Claude Code's Dynamic Workflows can fan out 1,000 subagents per run, but the runtime caps live concurrency at 16. Here's what that actual burst shape requires from an MCP server that exposes deploy and rollback.