Privacy & Terms MCP — Use Cases, Install & Live Demo

Why use it

Key features

Multi-jurisdiction: Korea (PIPA), EU (GDPR), US (CCPA/CPRA)
Interactive interview — sections conditional on business type
React UI components for consent modal + cookie banner
v3 modular routing: /privacy-terms → /privacy-kr | /privacy-eu | /privacy-global
Reflects 2025-04-21 Korean government template update

Live Demo

What it looks like in practice

privacy-terms-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "privacy-terms-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/kimlawtech/korean-privacy-terms.git",
        "~/.claude/skills/privacy-terms"
      ],
      "_inferred": false
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "privacy-terms-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/kimlawtech/korean-privacy-terms.git",
        "~/.claude/skills/privacy-terms"
      ],
      "_inferred": false
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "privacy-terms-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/kimlawtech/korean-privacy-terms.git",
        "~/.claude/skills/privacy-terms"
      ],
      "_inferred": false
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "privacy-terms-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/kimlawtech/korean-privacy-terms.git",
        "~/.claude/skills/privacy-terms"
      ],
      "_inferred": false
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "privacy-terms-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/kimlawtech/korean-privacy-terms.git",
        "~/.claude/skills/privacy-terms"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "privacy-terms-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/kimlawtech/korean-privacy-terms.git",
          "~/.claude/skills/privacy-terms"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add privacy-terms-skill -- git clone https://github.com/kimlawtech/korean-privacy-terms.git ~/.claude/skills/privacy-terms

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Privacy & Terms

Ship a Korean-compliant privacy policy for a SaaS launching in Korea

👤 Teams launching a product targeting Korean users ⏱ ~45 min intermediate

When to use: You're live in Korea within a week and need a PIPA-compliant 개인정보 처리방침 that reflects the 2025.4.21 guideline.

Prerequisites

Skill installed — git clone https://github.com/kimlawtech/korean-privacy-terms.git ~/.claude/skills/privacy-terms
Answers ready to interview questions — Know your data categories, retention periods, processors, transfers

Flow

Kick off the interview

/privacy-terms — jurisdiction: Korea. Service type: B2C SaaS. Begin the interview.✓ Copied

→ Skill asks about data categories, legal basis, third parties — one at a time
Answer and iterate

We collect email + login metadata. Retention: 3 years or on account deletion. Processors: AWS Seoul, Slack.✓ Copied

→ Skill incorporates answers; conditional sections light up (e.g. cross-border transfer disclosure)
Export

Export the final 개인정보 처리방침 as /legal/privacy-ko.md and the consent modal as React component.✓ Copied

→ Two artifacts on disk; consent modal compiles

Outcome: A draft privacy policy that matches the current KR guideline — your lawyer reviews, you ship.

Pitfalls

Copying last year's template — The 2025.4.21 update changed several required disclosures; rely on the skill's current template, not archived PDFs
Treating as legal advice — Have a Korean privacy counsel review before publish — this is a drafting aid

Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

privacy-terms-skill + filesystem

Write policy files and components to /legal and /src/components

Save /privacy-terms output to /legal/privacy-ko.md; components to src/components/consent/.✓ Copied

privacy-terms-skill + github

Open a PR with the legal update

Commit the new policy + components and open a PR 'legal: adopt 2025.4.21 KR template' tagged @legal-review.✓ Copied

privacy-terms-skill + web-design-skill

Style consent components to match your DESIGN.md tokens

Style ConsentModal per DESIGN.md primary/accent tokens; keep WCAG AA contrast.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
/privacy-terms	jurisdiction, service_type → routed to /privacy-kr \| /privacy-eu \| /privacy-global	Top-level entry; routes to the correct jurisdiction module	Claude API calls only
/privacy-kr	business details	Direct Korea-only invocation	free + Claude API
/privacy-eu	business details	Direct EU-only invocation	free + Claude API
/privacy-global	business details	US / global-default invocation	free + Claude API

Cost & Limits

What this costs to run

API quota: None beyond normal Claude usage
Tokens per call: Moderate — final policy is long-form prose
Monetary: Free (check repo license)
Tip: Interview once; re-run only the sections that change. The modular split lets you regenerate EU without re-doing KR.

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: Your business details are sent to Anthropic as part of normal Claude calls. Don't paste full customer lists or raw PII into answers.

This is a drafting aid, not legal advice. Every generated document must be reviewed by counsel licensed in the target jurisdiction before publishing.
Regulations change — regenerate against the skill's latest template before each major release, not once a year.

Troubleshooting

Common errors and fixes

Skill outputs pre-2025 Korean template

git pull inside ~/.claude/skills/privacy-terms; the repo tracks the guideline updates

Verify: Check the skill's README for the guideline date it reflects

EU policy missing SCC transfer section

You answered 'no transfers'. If data touches AWS us-east-1 or similar, say yes — the section only generates when triggered.

Verify: Re-interview with the correct transfer flag

Consent modal doesn't respect jurisdiction defaults

useJurisdiction() hook requires IP or locale detection; default is conservative (off) when unknown. Wire in a geoIP lib or Accept-Language fallback.

Alternatives

Privacy & Terms vs others

Alternative	When to use it instead	Tradeoff
Iubenda / Termly	You want a hosted, legally-warranted service	Paid; less editable; less dev-friendly
Hand-written policy	You have in-house counsel drafting from scratch	Most rigorous; most expensive; slow
copying a friend's policy	Don't	Worst option — templates fall out of sync with your actual practices

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills