실제 코드베이스 내용을 기반으로 개인정보 처리방침 및 EULA와 같은 법적 정책을 생성, 감사 및 유지 관리합니다.
다른 이름 PolicyForge/mcp, @policyforge/mcp
- 스타
- 0
- Tools
- 20
- 다운로드, 30일
- —
- 최신 버전
- 0.9.0
- 마지막 커밋
- 2026년 10월 31일
- 라이선스
- —
PolicyForge MCP란?
실제 코드베이스 내용을 기반으로 개인정보 처리방침 및 EULA와 같은 법적 정책을 생성, 감사 및 유지 관리합니다. 20개 도구를 제공합니다. 예: generate_policy, generate_baa, regenerate_policy.
프로젝트 README에서 생성된 요약
PolicyForge MCP server 정보
PolicyForge MCP Server를 사용하면 개발자가 코드베이스의 실제 내용을 분석하여 법적 문서를 작성하고 관리할 수 있습니다. 약관을 수동으로 작성하는 대신, AI 에이전트가 프로젝트를 스캔하여 종속성, 쿠키 사용 및 데이터 처리 패턴을 식별함으로써 정확한 개인정보 처리방침, EULA 및 서비스 이용약관을 생성합니다. 이를 통해 법적 고지 사항이 애플리케이션의 기술적 실체와 일치하도록 보장합니다.
사용자는 Claude 또는 ChatGPT와 같은 클라이언트에서 브라우저 기반 로그인을 위해 OAuth로 연결하거나, Cursor 및 Windsurf와 같은 도구에서 원격 HTTP 전송을 위해 API key를 사용할 수 있으며, npx를 사용하여 서버를 로컬에서 실행할 수도 있습니다. 이 서버는 코드 동작과 정책 텍스트 간의 격차를 찾는 audit_compliance 및 코드 변경으로 인해 기존 정책이 오래되었는지 감지하는 check_policy_freshness와 같은 특화된 도구를 제공합니다. 정책 생성에는 월간 할당량이 소모되지만, 감사 및 드리프트 감지 도구는 무제한으로 사용할 수 있습니다.
활용 사례
- 1자동화된 정책 생성AI 에이전트가 프로젝트 종속성 및 데이터 수집 방법을 스캔하도록 하여 GDPR 및 CCPA를 준수하는 개인정보 처리방침을 생성합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
PolicyForge MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 PolicyForge MCP 설치
$ claude mcp add --env 'POLICYFORGE_API_KEY=<YOUR_POLICYFORGE_API_KEY>' mcp -- npx -y @policyforge/mcpCursor에 PolicyForge MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@policyforge/mcp"
],
"env": {
"POLICYFORGE_API_KEY": "<YOUR_POLICYFORGE_API_KEY>"
}
}
}
}VS Code에 PolicyForge MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@policyforge/mcp"
],
"env": {
"POLICYFORGE_API_KEY": "<YOUR_POLICYFORGE_API_KEY>"
}
}
}
}VS Code CLI에 PolicyForge MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@policyforge/mcp"],"env":{"POLICYFORGE_API_KEY":"<YOUR_POLICYFORGE_API_KEY>"}}'Claude Desktop에 PolicyForge MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@policyforge/mcp"
],
"env": {
"POLICYFORGE_API_KEY": "<YOUR_POLICYFORGE_API_KEY>"
}
}
}
}Codex에 PolicyForge MCP 설치
$ codex mcp add mcp --env 'POLICYFORGE_API_KEY=<YOUR_POLICYFORGE_API_KEY>' -- npx -y @policyforge/mcpCodex config.toml에 PolicyForge MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@policyforge/mcp"] [mcp_servers.mcp.env] POLICYFORGE_API_KEY = "<YOUR_POLICYFORGE_API_KEY>"
Gemini CLI에 PolicyForge MCP 설치
$ gemini mcp add -s user -e 'POLICYFORGE_API_KEY=<YOUR_POLICYFORGE_API_KEY>' mcp npx -- -y @policyforge/mcpGemini settings.json에 PolicyForge MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@policyforge/mcp"
],
"env": {
"POLICYFORGE_API_KEY": "<YOUR_POLICYFORGE_API_KEY>"
}
}
}
}PolicyForge MCP 도구 20
README에서 감지됨generate_policygenerate_baaregenerate_policycheck_generationupdate_policyaudit_compliancecheck_policy_freshnesslist_policy_versionsrestore_policy_versionlist_policiesget_policydelete_policy
| generate_policy | — | |
| generate_baa | — | |
| regenerate_policy | — | |
| check_generation | — | |
| update_policy | — | |
| audit_compliance | — | |
| check_policy_freshness | — | |
| list_policy_versions | — | |
| restore_policy_version | — | |
| list_policies | — | |
| get_policy | — | |
| delete_policy | — |
도구 20개 모두 보기도구 수 줄이기
get_usageget_disclosure_checklistget_integration_guidelist_policy_typestypebusiness_typejurisdictionbaa_direction
| get_usage | — | |
| get_disclosure_checklist | — | |
| get_integration_guide | — | |
| list_policy_types | — | |
| type | — | |
| business_type | — | |
| jurisdiction | — | |
| baa_direction | — |
구성
POLICYFORGE_API_KEY필수비밀PolicyForge API key. Create one at https://policyforge.co/api-dashboard
| 이름 | 설명 | 유형 |
|---|---|---|
| POLICYFORGE_API_KEY | PolicyForge API key. Create one at https://policyforge.co/api-dashboard | 필수비밀 |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능policyforge/mcp is public and reachablegithub.com/policyforge/mcp ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-31github.com/policyforge/mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @policyforge/mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음99 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음20 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기PolicyForge MCP Server
Generate legal policies — privacy policies, terms of service, cookie policies, refund policies, EULAs, disclaimers, and HIPAA Business Associate Agreements — directly from your AI coding tools (Claude Code, Cursor, Windsurf, Claude Desktop) via the Model Context Protocol.
Ask your agent "generate a GDPR + CCPA privacy policy for this app" and it fills the details from your codebase, calls PolicyForge, and drops the policy straight into your project.
Try it free: compliance audits (audit_compliance), drift checks
(check_policy_freshness), and the scan rubric (get_disclosure_checklist)
are unlimited and never touch your quota — start with
"audit our compliance — does the privacy policy cover everything this code
actually does?". And the first time your account connects through MCP it gets
3 bonus policy generations on top of the free 2/month — enough to generate
privacy, terms, and cookie policies for a new project in one conversation.
Connect
Pick the row that matches your client. If you're unsure, start with A.
| How you sign in | Best for | |
|---|---|---|
| A. Remote + OAuth | Browser sign-in, no key to copy | Clients that support OAuth (Claude, ChatGPT) |
| B. Remote + API key | Authorization header |
Any client that can send a header |
| C. Local (npx) | POLICYFORGE_API_KEY env var |
Running the server as a local process |
All three expose the same tools. A and B need nothing installed.
A. Remote with OAuth (easiest)
No key to copy, no config file to edit. You'll need a PolicyForge account first — https://policyforge.co, free, no card.
1. Add the server. The -s user makes it available in every project rather
than only the directory you ran this in:
claude mcp add -s user --transport http policyforge https://policyforge.co/api/mcp
Note there is no --header. Omitting it is what makes the client use OAuth.
2. Restart your client. MCP config is read at startup, so a session that was already running won't see the new server.
3. Authenticate. Run /mcp, select policyforge, and press Enter:
policyforge · △ needs authentication
Your browser opens, you sign in and approve, and the client stores the token
itself. You should land back at /mcp showing ✔ connected · 16 tools.
To confirm from the other side, a key named MCP · <your client> appears at
https://policyforge.co/api-dashboard — that's the grant, and deleting it
revokes access.
Other clients differ in step 3: some prompt on first tool use rather than offering an explicit authenticate action.
B. Remote with an API key
For clients that don't do OAuth yet. Create a key at https://policyforge.co/api-dashboard, then:
claude mcp add --transport http policyforge https://policyforge.co/api/mcp \
--header "Authorization: Bearer pf_your_key_here"
For clients with URL-based MCP config (Cursor, Windsurf, and others):
{
"mcpServers": {
"policyforge": {
"url": "https://policyforge.co/api/mcp",
"headers": { "Authorization": "Bearer pf_your_key_here" }
}
}
}
C. Local (npx)
Prefer a local process? The server runs via npx — nothing to install
globally. Uses an API key from the environment, which is what the MCP spec
recommends for stdio transports.
Claude Code
claude mcp add policyforge \
--env POLICYFORGE_API_KEY=your_key_here \
-- npx -y @policyforge/mcp@latest
Cursor / Claude Desktop / Windsurf
Add to your MCP config (.cursor/mcp.json, claude_desktop_config.json, etc.):
{
"mcpServers": {
"policyforge": {
"command": "npx",
"args": ["-y", "@policyforge/mcp@latest"],
"env": {
"POLICYFORGE_API_KEY": "your_key_here"
}
}
}
}
On Windows, some clients need the command wrapped: set
"command": "cmd"and"args": ["/c", "npx", "-y", "@policyforge/mcp@latest"].
See https://policyforge.co/mcp for one-click installs (Cursor/VS Code) and per-client instructions — with your API key pre-filled when signed in.
Troubleshooting
- 401 — if you connected with OAuth, the authorization was revoked or
expired: reconnect and approve again. If you used an API key, it was deleted,
disabled, or mistyped (keys start with
pf_) — rotate or create one at https://policyforge.co/api-dashboard and restart the client. - 402 — generation quota exhausted. Free tier: 2 generations per calendar
month, plus a one-time bonus of 3 extra generations on first MCP connect.
Only
generate_policy/regenerate_policyconsume quota — audits and drift checks are free; ask your agent to runget_usageto see what's left. - 429 — request rate limit (free tier: 10/minute, 100/day); the response
includes
retry_after. - Server not listed in
/mcp— either the session started before you added it (restart the client; config is read at startup), or it was added to a different project scope.claude mcp add -s user …makes it available everywhere. - Tools missing — restart the client after config changes; on Windows use
the
cmdwrapper above. - "The redirect URI is not registered for this application" — the client is using a callback URL we haven't seen. Loopback callbacks work on any port (per RFC 8252), so this should be rare; report the exact URI and it can be supported.
More detail: https://policyforge.co/mcp#troubleshooting
Tools
| Tool | What it does |
|---|---|
generate_policy |
Generate a policy and return its Markdown content + hosted URL. Consumes one policy from your quota. |
generate_baa |
Generate a HIPAA Business Associate Agreement between a covered entity and a vendor handling PHI. Built from the clauses required by 45 CFR 164.504(e) and validated clause by clause. Pro plan; never publicly hosted. Consumes one policy from your quota. |
regenerate_policy |
Re-run the AI engine with changed business context — same ID and hosted URL, previous content saved as a version. |
check_generation |
Get the result of a generation that was still running when its tool returned a job ID (generation takes 40-60s; tools wait up to 45s). |
update_policy |
Edit a policy in place with find/replace edits or full content — same ID and hosted URL, so published links keep working. |
audit_compliance |
Gap analysis: compare what the code does (your scanned manifest) with what a policy discloses. |
check_policy_freshness |
Drift detection: diff the current codebase scan against the manifest stored at generation time. |
list_policy_versions |
Version history — a snapshot is saved before every update, regeneration, or restore. |
restore_policy_version |
Roll a policy back to any previous version (itself reversible). |
list_policies |
List policies on your account (filter by type/status, paginate). |
get_policy |
Fetch a single policy by ID, including full content. |
delete_policy |
Permanently delete a policy (its hosted URL stops working). |
get_usage |
Check your tier and remaining generation quota before generating. |
get_disclosure_checklist |
The codebase-scan rubric: which SDKs/patterns require disclosure and how findings map to generate_policy fields. |
get_integration_guide |
Copy-paste embed/link instructions for Next.js, React, plain HTML, or WordPress. |
list_policy_types |
List supported policy types, business types, and jurisdictions. |
The codebase-aware workflow
Your agent can read your project — so policies come from what the code actually does, not what you remember it doing:
get_disclosure_checklist→ agent scans dependencies, script tags, cookie writes, and outbound hosts against the rubric, and builds a stack manifest of what it foundgenerate_policywith the detected context +stack_manifest(stored server-side for drift detection)get_integration_guide→ agent wires the hosted policy into your footer- Later, after the stack changes:
check_policy_freshnessreports the drift,audit_complianceshows the concrete gaps, andregenerate_policyfixes them — same hosted URL, no broken links, previous version restorable
generate_policy inputs
Required: type, business_type, jurisdiction, company_name, contact_email
type—privacy_policy·terms_of_service·cookie_policy·refund_policy·eula·disclaimerbusiness_type—e-commerce·saas·healthcare·education·financial·fintech·real-estate·non-profit·consulting·media·mobile_app·otherjurisdiction— one or more ofgdprccpapipedalgpduseucaukaubrglobal(comma-separate to combine, e.g.gdpr,ccpa)
Optional context (improves output): website_url, service_description,
data_collection[], third_party_integrations[], data_retention,
user_accounts, payments, marketing, analytics, cookies,
children_data, sells_data, target_audience[], security_measures[],
governing_law, physical_address, dpo_email, consent_tracking,
hosting_enabled.
generate_baa inputs
A Business Associate Agreement is a contract between two named parties, not a published policy, so it takes its own tool and its own fields. Pro plan.
Required: acknowledge_contract (must be true), baa_direction,
company_name, contact_email, both parties' legal names and addresses,
baa_effective_date (YYYY-MM-DD), baa_services_description,
baa_phi_types[], baa_permitted_uses[], baa_governing_law_state.
baa_direction—covered_entity_to_vendor(you are the practice issuing the agreement) orbusiness_associate_to_client(you are the vendor offering it to a healthcare client)baa_phi_types[]— categories of PHI involved. Including"Substance use treatment records (42 CFR Part 2)"adds a Part 2 addendumbaa_permitted_uses[]— anything not listed here is not permitted by the agreement (45 CFR 164.504(e)(2)(i))
Optional: baa_electronic_phi (default true),
baa_uses_subcontractors (default false), baa_term_type,
baa_term_end_date, baa_breach_notification_days (1–60, default 30),
baa_return_or_destroy, baa_include_indemnification,
baa_include_insurance, baa_insurance_amount.
Every generated agreement is checked against the 15 clauses 45 CFR 164.504(e) requires before it is returned; an incomplete draft is refused rather than handed back. The result is still a draft for counsel to review, and it is never published at a public URL.
Configuration
Only needed for the local (npx) transport. Remote connections authenticate
over OAuth or an Authorization header instead.
| Env var | Required | Default | Purpose |
|---|---|---|---|
POLICYFORGE_API_KEY |
yes (local only) | — | Your PolicyForge API key. |
POLICYFORGE_API_URL |
no | https://policyforge.co |
Override the API base URL (self-host/testing). |
How it works
This server is a thin wrapper over the PolicyForge public REST API (/api/v1).
Every tool maps to one authenticated HTTP request, so quota, rate limiting, and
policy generation stay authoritative on the PolicyForge server — the MCP layer
holds no secrets beyond your API key and no business logic of its own.
License
MIT
PolicyForge MCP 질문
PolicyForge MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'POLICYFORGE_API_KEY=<YOUR_POLICYFORGE_API_KEY>' mcp -- npx -y @policyforge/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
PolicyForge MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
PolicyForge MCP는 어떤 도구를 제공하나요?
20개 도구를 제공합니다. 예: generate_policy, generate_baa, regenerate_policy, check_generation, update_policy.
사용 비용은 얼마인가요?
컴플라이언스 감사, 드리프트 체크 및 스캔 루브릭은 제한 없이 무료로 사용할 수 있습니다. 무료 티어에는 매월 2회의 정책 생성 기능이 포함되며, 첫 MCP 연결 시 3회의 추가 생성 보너스가 1회 제공됩니다.
어떤 종류의 정책을 생성할 수 있나요?
개인정보 처리방침, 서비스 이용약관, 쿠키 정책, 환불 정책, EULA, 면책 조항 및 HIPAA Business Associate Agreement를 생성할 수 있습니다.