MCP

Two weeks ago I wrote about what changes when you keep the model fixed and swap the harness. The short version: the wrapper matters more than people assume.

The previous article, Tool-Surface Compression, was about getting external functionality, entire APIs and systems, into the agent as token-efficiently as

2,500 API endpoints. Expose every one of them as an MCP tool and you get, according to Cloudflare, 1.17 million tokens for tool definitions alone, before the

Workflow automation used to be simple. Trigger fires, steps execute, data moves from A to B. Every branch is predetermined. Every outcome is scripted. The human

How Claude Sonnet 4.5 and GitHub Copilot helped us navigate the maze of custom Backstage integrations The Backstage Promise (and the Reality) Spotify's

Short read (~6–7 min) – focused on the operational side of Model Context Protocol (MCP) enablement. 1. Problem in Practice Single MCP servers are easy.

Introduction Model access alone rarely delivers differentiated organizational value. Real leverage appears when language models can safely invoke tools

The world of AI is evolving rapidly, and with it, the way we interact with APIs and infrastructure. At Infralovers, we're excited to explore how Postman's new

The Model Context Protocol (MCP) specification was introduced by AI research company Anthropic. Since its release, it has seen widespread adoption across