Posts

Under the Hood of an MCP Gateway: Registry, Auth, and Guardrails

If you have read about MCP gateways, you have probably seen them described in one tidy sentence: a single governed interface between AI agents and the tools they use. That sentence is accurate, but it hides all the interesting engineering. What actually happens, mechanically, when an agent asks a gateway "what tools do I have?" and then calls one? This article opens the box and walks through the three subsystems that do the real work—the registry that decides what an agent can discover, the authentication layer that proves identity on both sides, and the guardrail pipeline that inspects traffic as it flows. The aim is to give you a builder's mental model rather than a marketing summary. We will use a hosted enterprise MCP gateway as a running example of how these parts fit together, but every concept here applies to any gateway you might adopt or build. Where a configuration field is shown, treat the exact names as illustrative of one convention; the shape of the problem...

LLM FinOps: Controlling Spend at the Gateway

When a team ships its first large language model feature, the bill is usually small enough to ignore. A few thousand API calls, a modest invoice, no reason to worry. Then adoption spreads. A second product team adds a summarization endpoint, a support tool starts drafting replies, an internal agent begins calling the model in a loop, and suddenly the monthly invoice from one or more model providers has grown an order of magnitude with no one quite able to explain why. This is the moment most organizations discover that LLM spend behaves differently from traditional cloud spend, and that the financial discipline they built for servers and storage does not translate cleanly to tokens. FinOps, the practice of bringing engineering, finance, and product together to manage variable cloud cost, has a natural home in the world of language models. But applying it well requires a control point. You cannot manage what you cannot see, and you cannot enforce what you cannot intercept. The most effe...

What Is an MCP Gateway? The 2026 Guide to Governing Tool Calls

Over the past two years, the way software talks to large language models has settled into a recognizable shape. A model receives a prompt, reasons about it, and — increasingly — decides to call a tool: query a database, open a ticket, read a file, hit an internal API. That ability to act, not just answer, is what turns a chat model into an agent. And the moment an agent can act, the question stops being "is the answer good?" and becomes "should this action have been allowed at all?" The Model Context Protocol (MCP) is the emerging standard that makes those actions possible in a consistent way. It defines how an AI agent discovers and calls tools exposed by external systems. As MCP adoption grows, organizations find themselves running not one MCP server but dozens, each wrapping a different system, each with its own credentials, its own permissions, and its own blast radius. An MCP gateway is the piece of infrastructure that sits between agents and those servers to ...