Legal Context ProtocolMCP Integration
Model Context Protocol — LCP exposed as MCP tools, resources, and prompts so any MCP-compatible agent platform reaches legal context without per-platform integration.
This section is advisory and non-prescriptive. The illustrations describe current possibilities and limitations rather than canonical shapes. The MCP stewards are invited to publish authoritative LCP integration guidance for the protocol.
What it is
The standard for agent-to-tool connectivity. MCP servers expose tools, resources, and prompts to MCP-compatible agent platforms. See MCP as Delivery Mechanism 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 a 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 |
Tool-level annotations such as destructiveHint and openWorldHint signal that LCP-aware tools perform legally significant actions and that legal-context verification is expected before invocation.
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. Clients consuming multiple servers must accommodate the variance.
Steward invitation
The MCP stewards are invited to publish authoritative LCP MCP server guidance, including canonical tool, resource, and prompt registries.