MCP as Delivery Mechanism

This section is advisory.

The Model Context Protocol (MCP) is the open standard for agent-to-tool connectivity, supported across major AI platforms. MCP's architecture is specifically designed to be extended through new servers — which makes an LCP MCP server a natural delivery mechanism for legal context. Agents that already use MCP for other tools gain access to LCP-aware capabilities without per-platform integration.

An LCP MCP server can expose legal-context discovery, terms verification, signed acceptance recording, agreement-record management, and dispute initiation as MCP tools, resources, and prompts. The same server is usable regardless of which commerce, authorization, or settlement protocol the agent is operating under: the agent accesses legal context through MCP and executes the transaction through whichever protocol is in use. This protocol-independence is the architectural reason MCP is a useful delivery channel for LCP — it decouples the legal-context layer from the choice of commerce rail.

As an extension. The 2026-07-28 revision added an extensions field to client and server capabilities. Extensions are identified by a {vendor-prefix}/{extension-name} pair — official ones use io.modelcontextprotocol, and a third-party author SHOULD use a reversed domain they own — so an LCP extension may be published without upstream coordination. Where a server exposes capabilities, an extension declares a negotiated contract: the better fit where both parties need to establish, before any tool is called, that legal-context handling is available and what it requires.

The same revision moved MCP's core to a stateless model, removing the initialization handshake and the session header in favour of information carried on each request. Implementations should read the published 2026-07-28 text rather than inferring the negotiation surface from earlier revisions.

Concrete shapes of LCP-aware tools, resources, and prompts are illustrated in the MCP protocol page. The standard does not canonize a particular tool registry, URI scheme, or prompt set; the MCP stewards are invited to publish authoritative integration guidance.