Privacy & Terms MCP — 使用場景, 安裝 & 即時演示

為什麼要用

核心特性

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

即時演示

實際使用效果

privacy-terms-skill.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

~/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
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.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 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

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
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "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
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.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 使用伺服器物件陣列，而非映射。

~/.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"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

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

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： Privacy & Terms

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

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

何時使用： You're live in Korea within a week and need a PIPA-compliant 개인정보 처리방침 that reflects the 2025.4.21 guideline.

前置條件

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

步驟

Kick off the interview

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

→ 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.✓ 已複製

→ 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.✓ 已複製

→ Two artifacts on disk; consent modal compiles

結果： A draft privacy policy that matches the current KR guideline — your lawyer reviews, you ship.

注意事項

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

搭配使用： filesystem

組合

與其他 MCP 搭配，撬動十倍槓桿

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/.✓ 已複製

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.✓ 已複製

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.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫	成本
/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

成本與限制

運行它的成本

API 配額: None beyond normal Claude usage
每次呼叫 Token 數: Moderate — final policy is long-form prose
費用: Free (check repo license)
提示: Interview once; re-run only the sections that change. The modular split lets you regenerate EU without re-doing KR.

安全

權限、密鑰、影響範圍

憑證儲存： None

資料出站： 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.

故障排查

常見錯誤與修復

Skill outputs pre-2025 Korean template

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

驗證： 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.

驗證： 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.

替代方案

Privacy & Terms 對比其他方案

替代方案	何時用它替代	權衡
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

Privacy & Terms