266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
Your Ingress Is Now Your MCP Bouncer: What Traefik Hub's MCP Gateway Actually Enforces
Traefik Hub's MCP Gateway turns the ingress controller many self-hosted shops already run into the policy point for agent tool calls — OAuth discovery, JWT identity, task-based authorization, and session affinity in one middleware. A concrete breakdown of the five enforcement mechanics, a worked authorization example, and what gateway-mediated MCP means for standalone servers.
What Breaks When the Agent Calls Deploy: Production MCP Failure Modes and What a Deploy API Owes the Caller
Agent-tool calls fail in four repeatable ways: retries that double-execute, timeouts shorter than deploys, errors the model cannot act on, and silent definition drift. Each one dictates a concrete requirement for any deploy API that takes agents as callers.
A2A Turns One: What 150+ Organizations Standardizing Agent-to-Agent Messaging Means for a PaaS Whose Agents Deploy Apps
A2A hit v1.0 with 150+ organizations and production rollouts at Microsoft, AWS, Salesforce, SAP, and ServiceNow. Here is the MCP-vs-A2A routing rule, a worked deploy-agent delegation, and when a self-hosted PaaS should ship its own Agent Card endpoint.
Your AI Agent Can Now Restart Prod Postgres From Chat: What the Coolify–AnythingLLM MCP Bridge Costs in Audit and Rollback
An open-source MCP server lets an AI agent deploy, restart, and roll back Coolify apps from an AnythingLLM chat window. A threat-model teardown of what agent-driven deploys cost in scope, attribution, and reversibility — and the five-item checklist any agent-facing deploy server must pass.
Crossplane and AI: Why Agent-Operated Platforms Need Declarative APIs, Not Dashboards
CNCF's case that AI agents need API-first declarative infrastructure is right — but Crossplane's sprawling CRD surface is the wrong window into it. Agents need a small typed PaaS API over declarative machinery.
Dokploy Shipped 508 MCP Tools. The Community Deleted 95% of Them.
Dokploy's official MCP server mirrors every API endpoint as a tool — 508 of them, burning roughly 74k tokens before the first question. Community rivals cover the same API with 13 to 28 curated tools. The measured numbers behind the backlash, and five design rules for the next infrastructure MCP.
Building Agents That Don't Break Themselves: Fly.io's Sprite Safety Patterns and the Deploy-from-Chat Risk Model
Fly.io's June 2026 Sprite safety patterns — splitting the agent loop from execution, per-run credentials, and checkpoint restores — map directly onto what a deploy platform needs before agents can ship code: scoped credentials, audit logs, and guaranteed rollback.
Istio's Agentgateway Gambit: The Service Mesh Is Coming for Your Agent Traffic
Istio's experimental agentgateway support puts MCP tool calls, agent-to-agent sessions, and LLM routing inside the service mesh. What the KubeCon EU 2026 announcement changes for platform teams, and how close it is to production-ready.
Pinterest's MCP Servers Save 7,000 Engineering Hours a Month: What 66,000 Invocations Teach About Agent-Operated Infrastructure ROI
Pinterest's production MCP ecosystem handles 66,000 monthly tool calls across 844 engineers, saving an estimated 7,000 hours a month. A teardown of where those savings came from, how solid the math is, and which operations a smaller platform should expose to agents first.