Use LegalForge with your AI agent

LegalForge has an MCP server, a command-line tool and an HTTP API. All three run the same generator as the website: the document says what your answers say, and nothing is written by an AI model. It is a document generator, not a law firm, and it does not give legal advice.

What a key changes

No key is needed to connect, to list document types, or to generate. Without a key, generate_document is the free website generator: one complete privacy policy per email for one site, with a LegalForge credit line; other types come back as a preview. With a Business plan key (Authorization: Bearer lf_..., shown once when you subscribe and rotatable on your account page) every type is complete, unbranded and unlimited in sites. A key on another plan gets plan_feature; an invalid key gets HTTP 401. See pricing.

MCP tools

  • list_document_types: the six types, what each is for, which plans include it. Read-only.
  • list_services: the third-party services the policies describe by name (Stripe, Google Analytics, Firebase Crashlytics, AdMob and more): who runs each, what it receives, why, its own privacy policy and the vendor page that says so. Optional platform (web or app). Read-only; also GET https://privacypolicygenerator.tools/api/services and legalforge services.
  • store_forms: for a mobile app, the same service picks as Google Play Data safety answers (a CSV the Console imports) and an Apple App Privacy checklist (legalforge store-forms, POST /api/store-forms), each row quoting the vendor. Only the picked services; not legal advice. Read-only.
  • consent_banner: the same service picks as one inline cookie-banner snippet that matches your cookie policy (legalforge consent-banner, POST /api/consent-banner). Opt-in for the EU and UK, opt-out for the United States; the choice stays in the visitor's browser and the snippet contacts no server. Not legal advice. Read-only.
  • dpa: the same service picks as a Data Processing Agreement draft (the eight points of GDPR Article 28(3)) and a sub-processor table, each row restated from the vendor's own documentation (legalforge dpa, POST /api/dpa). A hosted copy serves the table with a dated change log at /p/<docId>/subprocessors. Not legal advice; it never says the agreement makes anyone compliant. Read-only.
  • embed_snippet: for a hosted document, the paste-once embed (script tag, HTML URL, WordPress shortcode, Shopify section; legalforge embed <docId>). It shows the text stored now, so a law-monitor update reaches your page without re-pasting. Read-only.
  • generate_document: { type, info } to Markdown. Every answer in info changes the text, so pass only practices you confirmed. It records the site against your plan's site limit, like the website does. It does not publish or host the document.

Claude Code

claude mcp add --transport http legalforge https://privacypolicygenerator.tools/mcp
# Business plan key (optional):
claude mcp add --transport http legalforge https://privacypolicygenerator.tools/mcp --header "Authorization: Bearer lf_YOUR_KEY"

Claude Desktop, claude.ai, Cursor and other clients

Add a remote MCP server with the URL https://privacypolicygenerator.tools/mcp. In Claude Desktop and claude.ai that is Settings, Connectors, Add custom connector. Clients that read a JSON config (Cursor's .cursor/mcp.json and similar) take:

{
  "mcpServers": {
    "legalforge": {
      "url": "https://privacypolicygenerator.tools/mcp",
      "headers": { "Authorization": "Bearer lf_YOUR_KEY" }
    }
  }
}

Leave out headers to use the free plan. claude.ai connectors cannot send a header, so they run on the free plan.

ChatGPT and Codex

Add https://privacypolicygenerator.tools/mcp as a remote (Streamable HTTP) MCP server in the client's connector or MCP settings. It works without a key.

CLI

npx legalforge types
npx legalforge generate privacy-policy --name "Acme" --url https://acme.example \
  --email [email protected] --personal-data --cookies --analytics > privacy.md
# Business plan key: legalforge login   (or LEGALFORGE_API_KEY=lf_...)

Raw MCP over HTTP

curl -X POST https://privacypolicygenerator.tools/mcp -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_document_types","arguments":{}}}'

Operated by Heron Networks LLC. Questions: support.