Open Agreements

io.github.open-agreementsPublished by GitHub account open-agreementsv0.10.2Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Finds standard U.S. legal agreement templates and fills them into reviewable DOCX drafts, locally or through a hosted endpoint.

What you can do
List and search agreement templates by keyword, topic, jurisdiction or source, with ranked results and compact catalog metadata. Read a single template's full field definitions before filling it. Fill a template with supplied field values and get a DOCX document back by URL or as a resource preview. For some field-selector templates, also generate a redline comparing the filled output against the standard form.
When to use it
Useful when an assistant needs to draft common agreements such as NDAs, SAFEs, NVCA documents or employment forms from standard, source-attributed templates, and hand a DOCX draft to a person for review.
Requirements
Either the hosted remote endpoint or the npm package run locally with npx; no authentication, environment variables or headers are declared. Local stdio mode keeps processing on the machine; some field-selector workflows download an official source document at runtime.
Before you install
Generated documents are drafts for human legal and business review, not legal advice, and are never automatically accepted or signed. Hosted template filling runs server-side, so document contents leave your machine; choose local mode for sensitive documents. Defaults fill omitted terms such as term length and governing law, so review every field.

Installation

In SourceWeft

  1. Open Open Agreements in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.open-agreements%2Fopen-agreements/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit 5a2b128

Tools

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.

Parameterslimitcursor

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.

Parametersqueryrequiredsourcecategorymax_results

get_template

Fetch a single template definition with full field metadata.

Parameterstemplate_idrequired

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.

Parametersvaluestemplaterequiredreturn_moderedline_baseinclude_redline

Version history

1
  1. v0.10.2LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts