266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
Every PaaS Now Speaks MCP: What Render, Fly, and Railway's Agent Bet Means for Whoever Owns the Server
In six weeks of summer 2026, Render, Fly.io, and Railway all shipped agent surfaces — OAuth MCP servers, disposable computers, chat plugins. A side-by-side inventory of what each actually exposes, the five things agent-operated deploys require, and the case for an open MCP server on machines you own.
MCP Went Stateless: Migrating a Deploy-and-Rollback Tool Server Behind an Ordinary Load Balancer
MCP's July 28, 2026 spec removes the handshake and Mcp-Session-Id, making every request self-describing. An 8-step migration plan for a deploy/logs/rollback tool server to replicas behind a plain load balancer — with per-request auth and an audit trail that survives the death of the session.
Railway's Summer of Agents: Sandboxes, Chat-Ops, and the Three Layers of Lock-In
Between June 5 and July 31, 2026, Railway shipped sandboxes, Docker-in-sandbox, preinstalled coding agents, a Slack/Discord platform agent, and ChatGPT/Grok plugins. A close read of what agents-as-tenants plus chat-as-console adds up to, the three layers where the all-in-one-vendor version locks you in, and the self-hosted equivalent on machines you own.
MCP Has 10,000 Servers but Three Production Gaps: Identity Propagation, Timeout Budgets, and Structured Errors for Deploy Agents
Ten thousand MCP servers and 97 million monthly SDK downloads made connecting agents to tools trivial — but an agent that can deploy and roll back production needs scoped identity, timeout budgets, and machine-readable errors first. This post designs that deploy surface, tool by tool.
Render Taught an AI Agent to Migrate Your Heroku App: What It Gets Right, What Still Needs You, and the Bill at the End
Render's open-source migration skill lets an AI agent move a Heroku app — dynos, config, Postgres — over MCP in minutes. A line-by-line test of the before/after bill, what the agent nails, where a human is still required, and the five capabilities your own fleet needs before migration becomes a prompt.
10,000 MCP Servers and No Human Wiring Them Up: What Server Cards and Stateless Operation Mean for Agents That Deploy Your Apps
MCP passed 10,000 public servers and is going stateless and self-describing, so agents will soon reach your deploy tools with no human wiring anything up. Here is the three-tier tool surface — observe freely, gate mutation, deny destruction — that survives contact with autonomous callers.
Defang's `/deploy` Skill Reveals the Three-Layer Stack Agent-Native PaaS Needs
Defang's deploy skill shows how agent runbooks, MCP actions, Docker Compose, and open Pulumi providers form an auditable agent-native PaaS stack.
Before AI Agents Operate Your Platform: The Catalog Hygiene Contract Your IDP Needs
Use a field-level catalog contract, a worked deploy example, and staged authority controls to let AI agents safely operate a self-hosted developer platform.
MCP Governance for Deploy APIs: A Playground-to-Production Control Plane
A practical Playground-to-production lifecycle for MCP deploy tools, with catalog review, policy-gateway controls, audience-bound tokens, approvals, and audit trails.