Part 2 of 14 · 2 min read
One plug shape, instead of an adapter for every pair
Think of USB-C. Before it, every device had its own plug and its own charger; with one plug shape, any device works with any charger.
In plain words: before a standard, connecting N agent applications to M systems takes up to N times M adapters. With a standard, each application implements the client side once and each system implements the server side once, so the cost becomes N plus M. A host keeps full ownership of the conversation, while a client is a thin connector it creates for exactly one server.
A worked example. The example's isolation test connects one host to two servers at once (a library and a calendar). It puts a secret sentence into the conversation history, then calls the calendar server with an ordinary query. Checking what each server actually received afterwards: neither server's call log contains the secret sentence, and the library server never saw the calendar query at all. The host held the whole conversation. Each server saw only the arguments of the calls addressed to it.
The key lines. From code/mini-mcp/host.py:
# from code/mini-mcp/host.py
def __init__(self, servers: dict, policy: Policy | None = None, approver: Callable | None = None, mode: str = "dual"):
self.policy = policy or Policy()
self.approver = approver or (lambda name, args: False)
self.clients: dict[str, Client] = {}
self.conns: dict[str, Connection] = {}
self.history: list[dict] = [] # the conversation lives HERE and nowhere else
self.prompts_shown = 0
self.entries: dict[str, ToolEntry] = {}
Read it as: the comment on self.history is not decoration. The host's __init__ builds one Client per server it is given. self.history is the single place in the whole design where the conversation is actually stored, and a server object, by construction, never gets a reference to it.
Host, client, server
The host is the application the person uses; it creates and manages the clients, controls connection permissions, enforces security and consent, and aggregates context from all of them. A client is a connector created by the host, one per server, that talks to exactly one server. A server is a program or service that offers tools, resources and prompts.
Example: the library server never seeing the word "dentist" is the host-client-server split doing its one job. A server that could read the whole conversation, or reach into another server's connection, would break the isolation the design relies on.