266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
Render's MCP Server Grows Teeth: OAuth Plus trigger_deploy Set the Agent-Deploy Bar
Render's July 2026 changelog added OAuth login and a trigger_deploy tool to its MCP server. This breakdown tables the full agent-deploy surface, names where Render's own docs stop, and lists what a self-hosted PaaS must ship to match it.
Your AI Agent Pushed Code and Nothing Deployed: Vercel's Git-Author Check vs the Age of Agent Committers
Vercel blocks deployments when the git commit author is not a recognized team member — a check that silently fails the moment an AI agent commits as itself. Four real cases, four working fixes, and why agent-first platforms authenticate the deploy call instead of the commit.
A2A Joins MCP Under One Roof: How to Hand an Ops Agent a Deploy Investigation Without Handing Over Deploy Authority
A2A joining MCP under the Agentic AI Foundation settles which protocol does what: A2A moves the diagnosis between agents, MCP moves capability between an agent and the platform. Here is the handoff design that keeps it that way — a worked deploy-investigation task, a three-tool audited MCP surface, and the identity, approval, and least-privilege invariants mapped to Kubernetes RBAC.
AGENTS.md Has a Neutral Home Now: What the Agentic AI Foundation Means for Deploy Platforms
OpenAI, Anthropic, and Block put MCP, goose, and AGENTS.md under the Linux Foundation's Agentic AI Foundation. Here is what neutral governance for the repo-instructions file means for deploy platforms — plus a copy-pasteable deploy-ready AGENTS.md.
Your Agent Can Call 7,000 SaaS APIs. Can It Deploy to a Machine You Own?
Arcade.dev gives agents 7,500+ SaaS tools behind brokered OAuth; Capix MCP gives them 37 tools that deploy models, provision GPUs, and emit signed receipts. Only one of those surfaces operates infrastructure you own — here is the checklist your PaaS MCP server still has to complete.
The Agent Is the Primary Tenant Now: Auditing CNCF's Platform Engineering 2.0
CNCF says internal platforms must be rebuilt for AI agents. A pillar-by-pillar audit of Platform Engineering 2.0 separates the genuinely new constraints — agent identity, MCP tool surfaces, machine-readable state — from old good practice, with a four-item checklist for self-hosted teams.
CNCF's 'Agentic Enterprise' Essay, Scored: What First-Class Agent Consumers Actually Require
CNCF's July 2026 agentic-enterprise essay lists what treating AI agents as first-class platform consumers requires. A row-by-row score against a self-hosted PaaS: five requirements ship, the shared context model is half-built, and the enterprise catalog baggage can be skipped.
A Czech Self-Hosting Hub Gave Claude Shell Access to Its Coolify Fleet: A 130-Line MCP Bridge Teardown
A Czech self-hosting hub wired Claude to its Coolify fleet through a 133-line MCP bridge — and handed the agent raw SSH instead of scoped deploy tokens. A code-level teardown of all seven tools, plus the five authorization rules a platform-owned MCP server needs.
Chat Deploys My App: What the Coolify–AnythingLLM MCP Bridge Proves, and the 5 Gaps a Render-Compatible MCP Server Closes
A community MCP server lets an LLM inspect, restart, and debug apps on a self-hosted Coolify box through AnythingLLM chat — but behind one shared API token sit a docker-socket tap and a root shell over SSH. Here is what the bridge proves, how Render's official MCP server scopes agent power instead, and the five gaps a Render-compatible MCP server still has to close.