266 posts tagged with "Model Context Protocol"
Content about the Model Context Protocol (MCP)
Pinterest Runs 66,000 MCP Tool Calls a Month: What Its Registry-and-Approval Blueprint Means for a Deploy-Tools MCP Server
Pinterest's production MCP fleet handles 66,000 tool calls a month behind a central registry and human approval gates. Here is the blueprint, and how it maps onto deploy, rollback, and logs tools for a self-hosted PaaS.
Railway Shipped Three Agent Tracks at Once: Remote MCP, railway agent, and One-Command Skills — Which Should a Self-Hosted PaaS Copy First?
Railway's April 2026 changelog shipped a 7-tool remote MCP server, a railway agent CLI command, and one-command skills install together. How the three tracks fit — and the copy order a self-hosted PaaS should follow: skills first, MCP second, hosted agent last.
Zeabur Calls Itself an AI DevOps Engineer. We Read the Fine Print.
Zeabur rebranded as an AI DevOps engineer with Agent Skills for Claude Code and Codex — but a head-to-head scorecard against Render's official MCP server shows the marketing is ahead of the authority. A grounded look at what each platform actually lets agents do.
A2A Hit 1.0 and Moved In With MCP: What Agent-to-Agent Handoff Actually Adds to Deploy-from-Chat
A2A reached 1.0 in March 2026 and joined MCP under the Agentic AI Foundation in August. Here is what agent-to-agent handoff concretely adds on top of a one-agent MCP deploy server, the exact extra surface a self-hosted PaaS must expose to support it, and when that work belongs on the roadmap.
Block's Buzz Topped GitHub Trending: What a Nostr Hive-Mind Gets Right (and Skips) Versus an MCP Deploy Surface
Block's Buzz hit #1 on GitHub trending with a Nostr-based workspace where humans and agents share one room. Here is what its chat-first model solves for multi-agent coordination — and why a deploy-from-chat platform still needs a typed, scoped MCP tool surface for production changes.
Goose Under the Linux Foundation: The Neutral Reference Client for Deploy-from-Chat
Block donated its Goose agent to the Linux Foundation's Agentic AI Foundation, alongside MCP and AGENTS.md. Here is why a PaaS team should certify its deploy and rollback MCP tools against Goose instead of one vendor's CLI — with a versioned deploy recipe to prove it.
Your Deploy Runbook Should Be a Skill, Not a Wiki Page
Agent Skills turn deploy, rollback, and log-triage runbooks from wiki pages agents never read into versioned skill bundles every major harness loads on demand. Here is the conversion — and why enforcement still belongs in the governed tool layer.
The MCP Roadmap's Five Priorities, Ranked by What They Cost a Self-Hosted Team
The August 2026 MCP roadmap names five priorities for the next spec release. Here is what each one means for teams running their own MCP servers, ranked by urgency, with an adoption sequence for owned infrastructure.
Qovery Says the Hard Part of Agent Deploys Is Governance, Not Access — They're Right
Qovery's CEO says the hard part of letting AI agents deploy is governance, not access — RBAC, budget limits, and audit trails enforced server-side. Why that validates the self-hosted playbook, and why agent-run migration makes the destination's meter the only bill that matters.