MCP Integration

Model Context Protocol — an LCP-aware server, or a negotiated extension under the 2026-07-28 revision.

This section is advisory and non-prescriptive. It describes what the host protocol permits, read from its own primary artifact. Where this page and the host protocol disagree, the host is correct — build from its schema, not from an example here.

What it is. The standard for agent-to-tool connectivity, stewarded by the Linux Foundation. MCP servers expose tools, resources, and prompts to MCP-compatible agent platforms. The current revision is 2026-07-28, which the specification calls "modern" and distinguishes from the "legacy" handshake-based revisions (2025-11-25 and earlier). That revision made MCP stateless — there is no negotiation handshake, and every request carries its own protocol version, client capabilities and identity in _meta — and in the same release removed protocol-level sessions and the Mcp-Session-Id header, removed ping and logging/setLevel, replaced resources/subscribe with subscriptions/listen, and added a server/discover RPC that servers MUST implement. It also added the extensions capability described below. Implementations should read the published 2026-07-28 text rather than inferring the surface from earlier revisions. See Section 10 for the architectural relationship between LCP and MCP.

Tier A — Available today. An LCP-aware MCP server can expose legal-context operations as tools, resources, and prompts without upstream coordination. Indicative shapes:

Tools.

Tool	Purpose
`get_legal_context`	Fetch a service's `legal-context.json` for a domain
`verify_terms`	Verify a terms document matches an `atrHash`
`accept_terms`	Record a signed acceptance over specified terms
`create_agreement`	Create an agreement record binding parties, terms, and jurisdiction
`get_agreement`	Retrieve an agreement record
`initiate_dispute`	File a dispute against an agreement
`get_dispute_status`	Check status of an active dispute

Resources.

Resource URI scheme	Content
`lcp://legal-context/{domain}`	The service's `legal-context.json`
`lcp://agreement/{id}`	An agreement record
`lcp://terms/{hash}`	A terms document by ATR hash
`lcp://dispute/{id}`	A dispute record and status

Prompts.

Prompt	Purpose
`review_terms`	Guided workflow for evaluating terms before acceptance
`dispute_evidence_assembly`	Structured assembly of dispute evidence

MCP's tool annotations describe environmental effect, not legal significance — destructiveHint means the tool may perform destructive updates to its environment, and openWorldHint that it interacts with external entities. No annotation conveys "legally significant action", and no client is specified to read one that way. An LCP-aware server SHOULD set the annotations truthfully for each tool's actual behaviour — discovery and verification are read-only and non-destructive; acceptance recording and dispute filing are not — rather than repurpose them as legal-significance signals.

Tier A — Available today, as an extension. The 2026-07-28 revision added an extensions field to ClientCapabilities and ServerCapabilities. Extensions are identified by a {vendor-prefix}/{extension-name} pair; official extensions use the io.modelcontextprotocol prefix, and a third-party author SHOULD use a reversed domain name they own. An LCP extension may therefore be published without upstream coordination:

{
  "capabilities": {
    "extensions": {
      "com.example/legal-context": {
        "minimumLevel": 2,
        "acceptedJurisdictions": ["..."]
      }
    }
  }
}

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.

Tier B — Forward work. Standardization of an LCP MCP server schema (canonical tool names, resource URI scheme, prompt definitions) through the MCP governance process would give clients consistent expectations across implementations.

Limitations. Without standardization, different LCP MCP server implementations may use different tool names, URI schemes, and prompt structures.

Steward invitation. The MCP stewards are invited to publish authoritative LCP MCP server guidance, including canonical tool, resource, and prompt registries.