mcp server
lexpact-mcp-server
lexpact-mcp-server - registries need a public source
Set up
Runs on your computer. Pick your agent and operating system.
Before you start
- Node.js 20 or newer
{
"mcpServers": {
"lexpact-mcp-server": {
"command": "npx",
"args": [
"-y",
"lexpact-mcp-server"
],
"env": {
"LEXPACT_API_KEY": "<your LEXPACT_API_KEY>"
}
}
}
}same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12
Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs
README
synced Nov 8, 2026LexPact MCP Server
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.
Setup
- Get an API key at lexpact.co.uk/dashboard/api-keys.
- Install dependencies:
cd mcp-server npm install - Add 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_templatesandgenerate_contractas needed.
Environment variables
| Var | Required | Purpose |
|---|---|---|
LEXPACT_API_KEY | Yes | Your LexPact API key. |
LEXPACT_API_BASE_URL | No | Override the API base URL (defaults to https://lexpact.co.uk/api/v1) — useful for testing against a local dev server. |
Manual test
LEXPACT_API_KEY=lp_live_... node index.js
Then connect any MCP client (e.g. the MCP Inspector: npx @modelcontextprotocol/inspector node index.js).