Open Agreements

io.github.open-agreements由 GitHub 账号 open-agreements 发布v0.10.2更新于 Oct 25, 2026

Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files.

已验证Streamable HTTP可网页运行效率与工作流文件与存储

概览

AI 生成的概览

查找美国标准法律协议模板,并将其填充为可供审阅的 DOCX 草稿,可在本地或通过托管端点运行。

可以做什么
按关键词、主题、司法辖区或来源列出和搜索协议模板,提供排序结果和精简目录信息。在填充前读取单个模板的完整字段定义。用提供的字段值填充模板,并通过 URL 或资源预览返回 DOCX 文档。对部分字段选择器模板,还会生成与标准表单对比的修订标记文档。
适用场景
适合助手需要基于有来源标注的标准模板起草 NDA、SAFE、NVCA 文件或雇佣表格等常见协议,并将 DOCX 草稿交由人工审阅的场景。
运行要求
可使用托管远程端点,或通过 npx 在本地运行 npm 包;未声明任何身份验证、环境变量或请求头。本地 stdio 模式在本机处理;部分字段选择器流程会在运行时下载官方源文档。
安装前请注意
生成的文档是供人工法律和业务审阅的草稿,不构成法律意见,也不会被自动接受或签署。托管填充在服务器端执行,文档内容会离开本机;敏感文档应选择本地模式。默认值会补全期限、管辖法律等未填条款,请逐项核对所有字段。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Open Agreements,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.open-agreements%2Fopen-agreements/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "open-agreements": {
      "type": "http",
      "url": "https://openagreements.org/api/mcp"
    }
  }
}

README

[OpenAgreements seal]

OpenAgreements

[npm version] [License: Apache 2.0] [CI] [codecov]

OpenAgreements helps people and software agents find primary-source-backed U.S. legal guidance and produce reviewable DOCX files from standard agreement templates.

What OpenAgreements does

  • Publishes jurisdiction-specific practice guides with citations to primary law.
  • Provides standard agreement templates with source and license metadata.
  • Fills templates locally through a CLI or over MCP.
  • Publishes review checklists and comparison surveys in human- and machine-readable formats.

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.

Fill your first agreement

Install the CLI locally, inspect the available forms, and fill the Common Paper Mutual NDA:

bash
npm install -g open-agreementsopen-agreements listopen-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.

Understand the workflow

text
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.

Choose your next step

Links: Website | Template Catalog | Docs | Trust | npm

Privacy and document handling

  • Local CLI and local stdio MCP processing stay on your machine.
  • Hosted MCP template filling runs server-side; filled documents are not stored after the response is returned.
  • Some field-selector workflows download an official source document at runtime.

Choose an execution mode that matches your document-sensitivity and internal policy requirements. See the trust-boundary status and security policy.

License

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.

来源:README.md,提交 5a2b128

工具

4

list_templates

List all available legal agreement templates as a paginated compact catalog. Returns lightweight metadata for discovery — call get_template for full per-field detail. Templates are returned in stable lexicographic order by template_id. For finding templates by topic, jurisdiction, or source, use search_templates instead.

输入参数limitcursor

search_templates

Search for legal agreement templates by keyword. Uses BM25 ranking to find the most relevant templates matching your query. Searches across template names, descriptions, categories, sources, and field definitions. Use this instead of list_templates when you know what kind of agreement you need.

输入参数query必填sourcecategorymax_results

get_template

Fetch a single template definition with full field metadata.

输入参数template_id必填

fill_template

Fill a legal agreement template with field values and return a document via URL or MCP resource preview metadata. For field-selector templates (e.g. NVCA), also generates a redline (track-changes) document comparing the filled output against the standard form.

输入参数valuestemplate必填return_moderedline_baseinclude_redline

版本历史

1
  1. v0.10.2最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分