MCP as Delivery Mechanism
An LCP MCP server is the natural delivery mechanism for making legal context discoverable and accessible to every agent in the ecosystem.
This section is advisory.
The Model Context Protocol (MCP) is the universal standard for agent-to-tool connectivity, with 97M+ monthly SDK downloads and support from every major AI platform (Claude, ChatGPT, Gemini, Copilot, Cursor, and others). MCP is governed by the Agentic AI Foundation (AAIF) under the Linux Foundation.
MCP's architecture is specifically designed to be extended through new servers. An LCP MCP server is the natural delivery mechanism for making legal context discoverable and accessible to every agent in the ecosystem.
LCP as MCP Tools
An LCP MCP server exposes legal context operations as callable tools:
| Tool | Description | Input |
|---|---|---|
get_legal_context | Fetch the LCP legal-context.json for a domain | { domain: string } |
verify_terms | Verify that a terms document matches its published hash | { termsUrl: string, expectedHash: string } |
accept_terms | Record cryptographic acceptance of specific terms | { agreementId: string, termsHash: string, signature: string } |
create_agreement | Create an agreement identity record binding parties, terms, and jurisdiction | { parties: Party[], termsUrl: string, jurisdiction: string } |
get_agreement | Retrieve an agreement identity record by ID | { agreementId: string } |
initiate_dispute | File a dispute with evidence against an agreement | { agreementId: string, evidence: Evidence[], claim: string } |
get_dispute_status | Check the status of an active dispute | { disputeId: string } |
LCP as MCP Resources
Legal context data exposed as readable resources:
| Resource URI | Content |
|---|---|
integra://legal-context/{domain} | LCP legal-context.json for a domain |
integra://agreement/{id} | Full agreement identity record |
integra://terms/{hash} | Terms document content |
integra://dispute/{id} | Dispute record and status |
LCP as MCP Prompts
Guided workflows for complex legal context operations:
| Prompt | Purpose |
|---|---|
review_terms | Guided workflow for an agent to review, evaluate, and decide on terms before acceptance |
dispute_evidence_assembly | Structured workflow for assembling dispute evidence from transaction records |
Integration Flow
1. Agent discovers LCP MCP server during initialization
2. Before any transaction, agent calls get_legal_context
or reads integra://legal-context/{domain}
3. Agent evaluates terms against its principal's policy
4. If terms acceptable: agent calls accept_terms (Level 3)
5. Transaction proceeds through commerce protocol (ACP, UCP, MPP, etc.)
6. Agreement identity created via create_agreement (Level 4)
7. If dispute arises: agent calls initiate_dispute with evidenceThis integration is protocol-agnostic. The same LCP MCP server works regardless of which commerce protocol the agent uses for the transaction. The agent accesses legal context through MCP and executes the transaction through ACP, UCP, MPP, x402, or any other protocol.
Deployment
An LCP MCP server can be deployed on any MCP-compatible hosting platform, including Cloudflare Workers (via McpAgent or createMcpHandler), AWS Lambda, or any HTTP server supporting the Streamable HTTP transport. The server is accessible to any MCP client — Claude, ChatGPT, Gemini, Copilot, and others — without per-platform integration.