Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@LexPact MCP Server Generate an NDA for a freelance designer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Exposes the LexPact contract generation API to Claude Desktop
(or any MCP client) as three tools: list_contract_templates, generate_contract,
get_contract. Thin proxy only — all validation and generation happens server-side
at https://lexpact.co.uk/api/v1, so structured, LLM-actionable error messages reach
Claude unchanged.
Get an API key at lexpact.co.uk/dashboard/api-keys.
Install dependencies:
cd mcp-server
npm installAdd to your Claude Desktop config (claude_desktop_config.json — Settings → Developer →
Edit Config):
{
"mcpServers": {
"lexpact": {
"command": "node",
"args": ["/absolute/path/to/mcp-server/index.js"],
"env": {
"LEXPACT_API_KEY": "lp_live_your_key_here"
}
}
}
}Restart Claude Desktop. Ask it to draft a contract — it will call list_contract_templates
and generate_contract as needed.
Related MCP server: Precedent
Var | Required | Purpose |
| Yes | Your LexPact API key. |
| No | Override the API base URL (defaults to |
LEXPACT_API_KEY=lp_live_... node index.jsThen connect any MCP client (e.g. the MCP Inspector: npx @modelcontextprotocol/inspector node index.js).
Generate a UK jurisdiction-aware contract (nda, service_agreement, freelance_agreement, recruiter_terms_of_business, or ir35_agreement). Collect all required fields through conversation before calling — never invent party names, addresses, dates, or amounts. On a validation error, read error.suggestion in the response and fix the request yourself.
Inputs: parties (required), jurisdiction (required), contract_type (required), scope_of_work (required), +12 more.
Retrieve a contract by id. Returns status "processing" while generation is still running (call again in about 30 seconds) and "completed" with the contract once done. content_markdown is always populated regardless of the original output_format — PDF URLs are only returned once, inline, by generate_contract.
Inputs: id (required).
List the 5 contract types LexPact can generate, their required/optional fields, and party role labels. Call this first if you don't already know the field requirements for a contract_type.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool targets a distinct phase of the lifecycle: discovery (list_contract_templates), creation (generate_contract), and retrieval (get_contract). The descriptions explicitly sequence them ('call this first', 'retrieve by id'), leaving no plausible misselection.
All three tools follow a strict verb_noun snake_case pattern (list_/generate_/get_ + contract object). Terminology is stable across names and descriptions.
Three tools is on the lean side, but each covers a necessary step and the server's scope is deliberately narrow (contract generation only). No tool feels redundant or padded.
The create-and-poll workflow is covered, but there is no way to list existing contracts, re-fetch a PDF URL after the initial generate response, or update/cancel a contract. Agents that lose the generate response or need an inventory are left with dead ends.
Contract-change authorization for AI agents: preflight a change to an API or MCP contract, get a signed decision, and verify the receipt offline. Only a granted change can proceed.
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
Connect MCP clients to 2,000+ AI models without managing provider API keys.
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
