LegalForge MCP Server
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., "@LegalForge MCP Server Create a privacy policy for Acme Inc in California using Stripe and Google Analytics"
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.
LegalForge MCP Server
Model Context Protocol (MCP) server for generating professional legal documents using AI.
Features
Privacy Policy - GDPR/CCPA compliant privacy policies
Terms of Service - Comprehensive terms for your website/app
Cookie Policy - Detailed cookie policies with consent info
Installation
npm install
npm run buildConfiguration
Set your Anthropic API key:
export ANTHROPIC_API_KEY=sk-ant-...Usage
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"legalforge": {
"command": "node",
"args": ["/path/to/legalforge-mcp/dist/index.js"],
"env": {
"ANTHROPIC_API_KEY": "sk-ant-..."
}
}
}
}Programmatic
echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"generate_legal_document","arguments":{"documentType":"privacy","parties":[{"name":"Acme Inc","role":"company","email":"legal@acme.com"}],"terms":{"websiteUrl":"https://acme.com","siteName":"Acme","services":"Google Analytics, Stripe, Intercom"},"jurisdiction":"California, USA"}}}' | node dist/index.jsTool: generate_legal_document
Inputs
Parameter | Type | Required | Description |
|
| ✓ | Type of legal document |
|
| ✓ | Parties involved (company, users) |
|
| ✓ | Document configuration |
|
| ✓ | Legal jurisdiction |
Party Object
Field | Type | Required | Description |
|
| ✓ | Party name |
|
| ✓ | Role |
|
| - | Physical address |
|
| - | Contact email |
Terms Object
Key | Description |
| Website URL |
| Display name for the site |
| Comma-separated list of services/technologies |
Output
Returns HTML document content (starting from <h2> tags).
Example
const result = await mcpClient.callTool("generate_legal_document", {
documentType: "privacy",
parties: [
{
name: "TechStartup Inc",
role: "company",
email: "privacy@techstartup.com"
}
],
terms: {
websiteUrl: "https://techstartup.com",
siteName: "TechStartup",
services: "Google Analytics, Stripe, AWS, Intercom"
},
jurisdiction: "European Union"
});
console.log(result.content[0].text); // HTML privacy policyDevelopment
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm start # Run compiled versionTemplate Usage
This MCP server serves as a template for building other MCP servers. Key patterns:
Tool registration with Zod schemas for validation
Prompt engineering with structured templates
Error handling with proper MCP error responses
Clean TypeScript setup with ESM modules
License
MIT
Available Tools
1 toolgenerate_legal_documentC
Generate professional legal documents (Privacy Policy, Terms of Service, Cookie Policy) using AI
Inputs: documentType (required), parties (required), terms (required), jurisdiction (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_legal_document' has a clear and distinct purpose.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (generate_legal_document).
A single tool is too few for a server named 'LegalForge MCP Server', which suggests a broader legal domain. This feels thin and incomplete for generating legal documents, as it lacks supporting tools like editing, reviewing, or managing templates.
The tool surface is severely incomplete for legal document generation. While 'generate_legal_document' covers creation, there are obvious gaps such as updating, deleting, listing, or customizing documents, which are essential for a full workflow.
Related MCP Connectors
One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
AI-powered legal document templates: NDAs, contracts, ToS, privacy policies. Not legal advice.
Compliant legal documents from your AI assistant: 1,100+ templates, 15 countries, free preview.
Connect your AI assistant to iubenda's privacy policy generator, terms and conditions generator, and cookie banner. Generate a privacy policy, cookie policy, and terms and conditions for your website or app, then set up a cookie banner that collects cookie consent from your visitors, all through natural language. Your policy is built from the services your site actually uses. Add them from iubenda's catalog of thousands of services, or run the cookie scanner to find the trackers and third-party services on your live site, then add what it finds to your policy. Configure your cookie consent banner (position, colors, and consent behavior) by asking, and update your documents whenever your site changes. Built for founders, agencies, and developers who need to meet the requirements of the General Data Protection Regulation (GDPR), the EU ePrivacy Directive, the California Consumer Privacy Act (CCPA) and other US state privacy laws, and privacy compliance rules across markets. Works in Claude, ChatGPT, and any MCP client that supports OAuth, with every iubenda plan, including the free one. Your assistant asks before anything final or permanent, like finalizing a policy or deleting a site.
