Legalithm — EU AI Act compliance in your coding loop

Shipping an AI feature to EU users? The Act applies — Article 50 transparency from Aug 2026, high-risk obligations from Dec 2027. Catch it where you code, in seconds. Free, open-source, offline.

Quickstart

npx legalithm setup   # wires Claude Code + Cursor (hooks, editor rule, MCP config)
npx legalithm init    # writes a dated, cited compliance/legalithm.json
npx legalithm check   # re-verify; non-zero exit on drift (for CI)

Three surfaces

1. Editor — an offline MCP server (legalithm-mcp-server) exposing 4 tools (classify, explain_obligation, generate_disclosure, check_record). No API key, no network.
2. Repo — legalithm init writes a dated, cited compliance/legalithm.json that records your AI system's risk tier and the obligations behind it.
3. CI — legalithm check and the GitHub Action fail the build when the committed record drifts — because your app changed or the law changed under you.

MCP config

Add the offline server to Claude Code or Cursor:

{
  "mcpServers": {
    "legalithm": {
      "command": "npx",
      "args": ["-y", "legalithm-mcp-server"]
    }
  }
}

GitHub Action

# .github/workflows/ai-act.yml
name: AI Act
on: [pull_request]
jobs:
  ai-act:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: legalithm/legalithm/packages/action@v1
        with:
          api-key: ${{ secrets.LEGALITHM_API_KEY }}

Honest framing

A cited starting point that tells you when to get a human — not legal advice. When unsure, it flags the result for review instead of guessing. Every output is checked against Regulation (EU) 2024/1689; it is not a certification.

Links

• Full docs: https://www.legalithm.com/en/developers/docs
• Landing: https://www.legalithm.com/en/developers

License

MIT