OpenAgreements
OpenAgreements helps people and software agents find primary-source-backed U.S. legal guidance and produce reviewable DOCX files from standard agreement templates.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @open-agreements/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add open-agreements-open-agreements -- npx -y @open-agreements/open-agreements@0.10.2在終端機中執行。
{ "mcpServers": { "open-agreements-open-agreements": { "command": "npx", "args": [ "-y", "@open-agreements/[email protected]" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
OpenAgreements provides legal information and document mechanics, not legal advice. It does not decide whether a form or clause is right for a transaction, and generated documents are drafts for human review.
The project’s longer-term goal is a citable conformance layer for legal AI: primary law becomes inspectable requirements, an AI can check a document against them, and a lawyer owns the final call. Read Why OpenAgreements Exists for the rationale; this README stays focused on using the project.
Install the CLI locally, inspect the available forms, and fill the Common Paper Mutual NDA:
npm install -g open-agreements
open-agreements list
open-agreements fill common-paper-mutual-nda \
--set party_1_name="Jane Doe" \
--set party_1_company="Acme Manufacturing, Inc." \
--set party_2_name="John Smith" \
--set party_2_company="Northeast Logistics LLC" \
--set effective_date="2026-07-15" \
--set purpose="Evaluating a potential logistics relationship" \
--output mutual-nda.docx
The last command writes mutual-nda.docx. Open it in Word or another DOCX
viewer and review every filled term before signature. Defaults supply the
standard one-year term, Delaware governing law, and other omitted cover terms;
the CLI reports any priority fields that still need attention.
For a complete, copyable example and field-review steps, follow the quick start.
standard form + source and license metadata
→ supplied field values
→ validation and local rendering
→ reviewable DOCX
→ human legal and business review
The standard form is authoritative until rendering. Your supplied values become the transaction-specific inputs. The generated DOCX is an output for review; it is never automatically accepted or signed.
The legal-content path is separate: practice guides cite primary sources, surveys compare jurisdictions, and checklists turn requirements into review steps. Those materials can inform a decision, but they do not mutate an agreement.
Links: Website | Template Catalog | Docs | Trust | npm
Choose an execution mode that matches your document-sensitivity and internal policy requirements. See the trust-boundary status and security policy.
Project code is licensed under Apache License 2.0. Content retains its
source-specific license. See the licensing reference
and each template's metadata.yaml before redistribution or modification.
Open-source legal template filling CLI and library
{ "mcpServers": { "open-agreements-open-agreements": { "command": "npx", "args": [ "-y", "@open-agreements/[email protected]" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
@open Agreements/open Agreements 透過 stdio 在本機執行。
上次檢查時間:2026-11-16。 Open-source legal template filling CLI and library