266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
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.
Your MCP Server Doesn't Know Who's Deploying. WorkOS's OAuth 2.1 Stack Fixes That
Most MCP servers still trust a bearer token in an env var. WorkOS's May 2026 OAuth 2.1 stack — CIMD, Resource Indicators, and on-behalf-of token exchange — finally answers the question a deploy-authority MCP server can't skip: which agent, acting for whom, just asked to ship to production?
Canine's MCP Server Can Deploy — Coolify's Still Can't: A Tool-by-Tool Audit
Canine's built-in MCP server ships one write tool — DeployProject — where Coolify's stays fully read-only. Here's the exact tool list across Canine, Coolify, and Dokploy, and what Canine's Kubernetes-native architecture actually buys over each.
Pulumi Neo Is GA and Reads Your Terraform State Directly — Here's Why bex's Deploy API Won't
Pulumi Neo reads live Terraform and CloudFormation state directly and executes changes inside it. bex's MCP server calls a fixed, enumerable set of verbs instead. Here's the concrete case for why an agent that can create and destroy production infrastructure needs to know which shape it's actually operating under.
10,000 MCP Servers Later, the Hard Part Isn't Building One — It's Being Found and Trusted
MCP passed 10,000 public servers and 97 million monthly downloads in 2026 — but 52% of those servers are abandoned. Here's what building bex's own MCP server into that ecosystem actually requires: the protocol's stateless rewrite, the tool-poisoning threat class, and why shipping one isn't a differentiator anymore.
AWS Built a Five-Step AI Agent Just to Pick a Service
AWS's deploy-on-aws plugin takes five steps and three MCP servers to deploy an app because it's solving a 200-service menu problem. Here's what happens to that step count on a platform that never had the menu — and the one step that stays hard everywhere.
Backstage Ships MCP Tokens for Claude and Cursor: What Exposing a Golden-Path IDP to AI Agents Actually Requires
Backstage 1.43 lets Claude and Cursor call your golden-path Scaffolder actions with a short-lived, per-user token instead of a shared secret. Here's the actual config, the failure mode an unscoped action list creates, and what a self-hosted PaaS's own MCP server needs to copy.
Better-PaaS Ships Scoped Agent Tokens for Cursor and Claude Code — What an AGPL Self-Hosted PaaS Choosing Managed Databases Over bex's Non-Goal Reveals
Better-PaaS, a single-maintainer AGPL project, ships three-tier scoped agent tokens and seven MCP tools for Cursor and Claude Code — a concrete look at what that buys against bex's own coarser key model, and where Better-PaaS's bundled managed databases trade convenience for the high-availability story a single VPS can't back.