@open-agreements/open-agreements 0.6.2 → 0.7.3

package/GEMINI.md

@@ -0,0 +1,25 @@
+# OpenAgreements — Local MCP Extension Context
+
+This extension is for local OpenAgreements workflows using two MCP servers:
+
+1. `contracts-workspace-mcp` (`@open-agreements/contracts-workspace-mcp`)
+- Workspace setup planning (`workspace_init`)
+- Catalog validation/fetch (`catalog_validate`, `catalog_fetch`)
+- Status generation and lint (`status_generate`, `status_lint`)
+
+2. `contract-templates-mcp` (`@open-agreements/contract-templates-mcp`)
+- Template discovery (`list_templates`)
+- Template inspection (`get_template`)
+- Template drafting/fill output (`fill_template`)
+
+## Trust Boundary
+
+Both MCP servers run locally via stdio and operate on local filesystem paths.
+No hosted MCP endpoint is required for extension operation.
+
+## Recommended Flow
+
+1. Use `workspace_init` to plan folder structure and collaboration files.
+2. Use `list_templates` / `get_template` to pick and inspect the contract template.
+3. Use `fill_template` to render a local DOCX output.
+4. Use workspace status tools to track draft/executed lifecycle state.

package/README.md

@@ -5,7 +5,7 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 [![Agent Skill](https://img.shields.io/badge/agent--skill-open--agreements-purple)](https://skills.sh)
 [![CI](https://github.com/open-agreements/open-agreements/actions/workflows/ci.yml/badge.svg)](https://github.com/open-agreements/open-agreements/actions/workflows/ci.yml)
-[![MCP Server Status](https://img.shields.io/endpoint?url=https%3A%2F%2Fopenagreements.ai%2Fapi%2Fstatus%3Fformat%3Dshields)](https://openagreements.openstatus.dev/)
+[![MCP Server Status](https://img.shields.io/endpoint?url=https%3A%2F%2Fopenagreements.org%2Fapi%2Fstatus%3Fformat%3Dshields)](https://openagreements.openstatus.dev/)
 [![codecov](https://img.shields.io/codecov/c/github/open-agreements/open-agreements/main)](https://app.codecov.io/gh/open-agreements/open-agreements)
 [![GitHub stargazers](https://img.shields.io/github/stars/open-agreements/open-agreements?style=social)](https://github.com/open-agreements/open-agreements/stargazers)
 [![Tests: Vitest](https://img.shields.io/badge/tests-vitest-6E9F18)](https://vitest.dev/)
@@ -49,7 +49,7 @@ Fill standard legal agreement templates and produce signable DOCX files. Templat
 
 OpenAgreements supports two execution modes with different trust boundaries:
 
-- Hosted remote MCP connector (`https://openagreements.ai/api/mcp`) for fast setup in Claude.
+- Hosted remote MCP connector (`https://openagreements.org/api/mcp`) for fast setup in Claude.
 - Fully local package execution (`npx`, global install, or local stdio MCP package) for machine-local workflows.
 
 There is no global default mode recommendation. Choose based on document sensitivity, internal policy, and workflow speed needs. See `docs/trust-checklist.md` for a 60-second data-flow summary.
@@ -125,7 +125,7 @@ This repository includes a Cursor plugin manifest with MCP wiring:
 
 The default MCP setup in `mcp.json` includes:
 
-- Hosted OpenAgreements MCP connector (`https://openagreements.ai/api/mcp`)
+- Hosted OpenAgreements MCP connector (`https://openagreements.org/api/mcp`)
 - Local workspace MCP server (`npx -y @open-agreements/contracts-workspace-mcp`)
 - Local template drafting MCP server (`npx -y @open-agreements/contract-templates-mcp`)
 
@@ -402,7 +402,7 @@ Template content is licensed by their respective authors — CC BY 4.0 (Common P
 ## Privacy
 
 - **Local mode** (`npx`, global install, stdio MCP): all processing happens on your machine. No document content is sent externally.
-- **Hosted mode** (`https://openagreements.ai/api/mcp`): template filling runs server-side. No filled documents are stored after the response is returned.
+- **Hosted mode** (`https://openagreements.org/api/mcp`): template filling runs server-side. No filled documents are stored after the response is returned.
 
 See our [Privacy Policy](https://usejunior.com/privacy_policy) for details.
 

package/content/external/yc-safe-discount/metadata.yaml

@@ -1,4 +1,5 @@
 name: YC Post-Money SAFE — Discount
+category: safes
 description: Y Combinator's Post-Money SAFE (Simple Agreement for Future Equity) with a discount rate and no valuation cap.
 source_url: https://www.ycombinator.com/documents
 version: '2024.12'

package/content/external/yc-safe-mfn/metadata.yaml

@@ -1,4 +1,5 @@
 name: YC Post-Money SAFE — MFN
+category: safes
 description: >-
   Y Combinator's Post-Money SAFE (Simple Agreement for Future Equity) with a most favored nation (MFN) provision, no
   valuation cap, and no discount.

package/content/external/yc-safe-pro-rata-side-letter/metadata.yaml

@@ -1,4 +1,5 @@
 name: YC Pro Rata Side Letter
+category: safes
 description: >-
   Y Combinator's Pro Rata Side Letter, granting the investor pro rata rights in connection with a Post-Money SAFE
   investment.

package/content/external/yc-safe-valuation-cap/metadata.yaml

@@ -1,4 +1,5 @@
 name: YC Post-Money SAFE — Valuation Cap
+category: safes
 description: >-
   Y Combinator's Post-Money SAFE (Simple Agreement for Future Equity) with a valuation cap and no discount. The most
   common early-stage investment instrument.

package/content/recipes/nvca-certificate-of-incorporation/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Certificate of Incorporation
+category: venture-financing
 description: >-
   Amended and restated certificate of incorporation for venture-backed Delaware corporations, defining preferred stock
   rights, preferences, and privileges.

package/content/recipes/nvca-certificate-of-incorporation/replacements.json

@@ -1,6 +1,6 @@
 {
   "INCORPORATIONOF > [_________]": "{company_name}",
-  "[____________], a corporation": "{company_name}",
+  "[____________], a corporation > [____________]": "{company_name}",
   "name of this corporation is > [_______________]": "{company_name}",
   "registered agent at such address is > [_____________________]": "{registered_agent_name}",
   "State of Delaware is > [_____________]": "{registered_agent_address}",

package/content/recipes/nvca-indemnification-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Indemnification Agreement
+category: venture-financing
 description: >-
   Director and officer indemnification agreement for venture-backed companies, providing indemnification and advancement
   of expenses.

package/content/recipes/nvca-investors-rights-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Investors' Rights Agreement
+category: venture-financing
 description: >-
   Investors' rights agreement for venture financings, covering registration rights, information rights, board observer
   rights, and protective provisions.

package/content/recipes/nvca-management-rights-letter/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Management Rights Letter
+category: venture-financing
 description: Management rights letter granting ERISA-qualifying management rights to venture capital fund investors.
 source_url: https://nvca.org/wp-content/uploads/2025/12/NVCA-2020-Management-Rights-Letter-1-1.docx
 source_version: '2020'

package/content/recipes/nvca-rofr-co-sale-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Right of First Refusal and Co-Sale Agreement
+category: venture-financing
 description: >-
   Right of first refusal and co-sale agreement for venture financings, restricting transfer of founder shares and
   providing investor co-sale rights.

package/content/recipes/nvca-stock-purchase-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Stock Purchase Agreement
+category: venture-financing
 description: >-
   Series preferred stock purchase agreement for venture capital financings, covering purchase terms, representations,
   and closing conditions.

package/content/recipes/nvca-voting-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: NVCA Model Voting Agreement
+category: venture-financing
 description: >-
   Standard-form voting agreement for venture capital financings, covering board composition, drag-along rights, and
   stockholder voting obligations.

package/content/templates/bonterms-mutual-nda/metadata.yaml

@@ -1,4 +1,5 @@
 name: Bonterms Mutual NDA
+category: confidentiality
 description: >-
   Cover page for the Bonterms Mutual NDA (Version 1.0). The standard terms are incorporated by reference from
   bonterms.com.
@@ -47,6 +48,88 @@ fields:
     description: Courts with jurisdiction over disputes
     default: courts located in San Francisco, California
     section: Legal
+  - name: party_1_signatory_type
+    type: enum
+    description: Whether Party 1 signatory is an entity or individual
+    default: entity
+    options: [entity, individual]
+    section: Signatures
+  - name: party_1_signatory_name
+    type: string
+    description: Full name of the person signing for Party 1
+    section: Signatures
+  - name: party_1_signatory_title
+    type: string
+    description: Title of the person signing for Party 1
+    section: Signatures
+  - name: party_1_signatory_company
+    type: string
+    description: Company of the signatory for Party 1 (defaults to party_1_name)
+    section: Signatures
+  - name: party_1_email
+    type: string
+    description: Notice email address for Party 1
+    section: Signatures
+  - name: party_1_address
+    type: string
+    description: Notice postal address for Party 1
+    section: Signatures
+  - name: party_2_signatory_type
+    type: enum
+    description: Whether Party 2 signatory is an entity or individual
+    default: entity
+    options: [entity, individual]
+    section: Signatures
+  - name: party_2_signatory_name
+    type: string
+    description: Full name of the person signing for Party 2
+    section: Signatures
+  - name: party_2_signatory_title
+    type: string
+    description: Title of the person signing for Party 2
+    section: Signatures
+  - name: party_2_signatory_company
+    type: string
+    description: Company of the signatory for Party 2 (defaults to party_2_name)
+    section: Signatures
+  - name: party_2_email
+    type: string
+    description: Notice email address for Party 2
+    section: Signatures
+  - name: party_2_address
+    type: string
+    description: Notice postal address for Party 2
+    section: Signatures
+  - name: party_1_signatory_name_and_title
+    type: string
+    description: Computed display field (Name, Title)
+    required: false
+    section: Signatures
+  - name: party_2_signatory_name_and_title
+    type: string
+    description: Computed display field (Name, Title)
+    required: false
+    section: Signatures
+  - name: party_1_notice_email_check
+    type: string
+    description: Computed checkbox glyph for email notice
+    required: false
+    section: Signatures
+  - name: party_1_notice_postal_check
+    type: string
+    description: Computed checkbox glyph for postal notice
+    required: false
+    section: Signatures
+  - name: party_2_notice_email_check
+    type: string
+    description: Computed checkbox glyph for email notice
+    required: false
+    section: Signatures
+  - name: party_2_notice_postal_check
+    type: string
+    description: Computed checkbox glyph for postal notice
+    required: false
+    section: Signatures
 priority_fields:
   - party_1_name
   - party_2_name

package/content/templates/bonterms-mutual-nda/signing.yaml

@@ -0,0 +1,35 @@
+signers:
+  - role: party_1
+    nameField: party_1_signatory_name
+    signatureField: sig_party_1
+    dateField: date_party_1
+    routingOrder: 1
+  - role: party_2
+    nameField: party_2_signatory_name
+    signatureField: sig_party_2
+    dateField: date_party_2
+    routingOrder: 2
+
+providerAnchors:
+  docusign:
+    sig_party_1: "/sn1/"
+    sig_party_2: "/sn2/"
+    date_party_1: "/ds1/"
+    date_party_2: "/ds2/"
+  dropboxsign:
+    sig_party_1: "[sig|req|signer1]"
+    sig_party_2: "[sig|req|signer2]"
+    date_party_1: "[date|req|signer1]"
+    date_party_2: "[date|req|signer2]"
+  adobesign:
+    sig_party_1: "{{sig1_es_:signer1:signature}}"
+    sig_party_2: "{{sig2_es_:signer2:signature}}"
+    date_party_1: "{{date1_es_:signer1:date}}"
+    date_party_2: "{{date2_es_:signer2:date}}"
+  pandadoc:
+    sig_party_1: "{{signature:party_1}}"
+    sig_party_2: "{{signature:party_2}}"
+    date_party_1: "{{date:party_1}}"
+    date_party_2: "{{date:party_2}}"
+
+emailSubjectTemplate: "Bonterms Mutual NDA — {{party_1_name}} / {{party_2_name}}"

package/content/templates/bonterms-professional-services-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Bonterms Professional Services Agreement
+category: professional-services
 description: >-
   Cover page for the Bonterms Professional Services Agreement (Version 1.2). The standard terms are incorporated by
   reference from bonterms.com.

package/content/templates/closing-checklist/metadata.yaml

@@ -1,4 +1,5 @@
 name: Closing Checklist
+category: other
 description: >-
   A stage-first, document-first closing checklist that tracks canonical
   documents, checklist entries, signatories, action items, and issues.

package/content/templates/common-paper-ai-addendum/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper AI Addendum
+category: data-compliance
 description: >-
   An AI addendum cover page and standard terms, based on Common Paper's standard form. Adds AI-specific provisions to an
   existing agreement, covering model training, input/output rights, and AI usage policies.

package/content/templates/common-paper-ai-addendum-in-app/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper AI Addendum In-App
+category: data-compliance
 description: >-
   An in-app AI addendum based on Common Paper's standard form. A streamlined version of the AI addendum designed to be
   accepted electronically within an application.

package/content/templates/common-paper-amendment/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Amendment
+category: deals-partnerships
 description: >-
   An amendment template for modifying existing agreements, based on Common Paper's standard form. References the
   original agreement and details the specific changes being made.

package/content/templates/common-paper-business-associate-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Business Associate Agreement
+category: data-compliance
 description: >-
   A HIPAA business associate agreement cover page and standard terms, based on Common Paper's standard form. Covers the
   use and protection of protected health information (PHI) between a covered entity and a business associate.

package/content/templates/common-paper-cloud-service-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Cloud Service Agreement
+category: sales-licensing
 description: >-
   A cloud service agreement with order form and framework terms, based on Common Paper's standard terms. Covers SaaS
   subscriptions, payment, SLAs, liability, and data processing. Includes full Standard Terms v2.1.

package/content/templates/common-paper-csa-click-through/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper CSA Click-Through
+category: sales-licensing
 description: >-
   A click-through cloud service agreement based on Common Paper's standard terms. Designed for self-serve SaaS products
   where the customer accepts terms online rather than negotiating a paper agreement.

package/content/templates/common-paper-csa-with-ai/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper CSA With AI
+category: sales-licensing
 description: >-
   A cloud service agreement with AI provisions, key terms, and standard terms, based on Common Paper's standard form.
   Extends the standard CSA with AI-specific terms covering model training, input/output rights, and AI usage policies.

package/content/templates/common-paper-csa-with-sla/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper CSA With SLA
+category: sales-licensing
 description: >-
   A cloud service agreement with SLA provisions, key terms, and standard terms, based on Common Paper's standard form.
   Includes uptime targets, response times, and support schedules alongside full CSA terms.

package/content/templates/common-paper-csa-without-sla/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper CSA Without SLA
+category: sales-licensing
 description: >-
   A cloud service agreement with key terms and standard terms, based on Common Paper's standard form. Covers SaaS
   subscriptions, payment, liability, and data processing.

package/content/templates/common-paper-data-processing-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Data Processing Agreement
+category: data-compliance
 description: >-
   A data processing agreement cover page and standard terms, based on Common Paper's standard form. Covers GDPR and data
   protection compliance, including processor/controller roles, data transfers, subprocessors, and security measures.

package/content/templates/common-paper-design-partner-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Design Partner Agreement
+category: deals-partnerships
 description: >-
   A design partner agreement cover page and standard terms, based on Common Paper's standard form. Covers partnerships
   where a company provides early access to a product in development in exchange for feedback and collaboration.

package/content/templates/common-paper-independent-contractor-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Independent Contractor Agreement
+category: professional-services
 description: >-
   An independent contractor agreement based on Common Paper's standard form. Covers the engagement of an independent
   contractor, including scope of services, rates, payment, timeline, and governing law.

package/content/templates/common-paper-letter-of-intent/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Letter of Intent
+category: deals-partnerships
 description: >-
   A letter of intent template for SaaS and technology deals, based on Common Paper's standard form. Outlines product,
   timeline, fees, and references an existing NDA.

package/content/templates/common-paper-mutual-nda/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Mutual NDA
+category: confidentiality
 description: >-
   A mutual non-disclosure agreement cover page based on Common Paper's standard terms. The cover page references the
   Standard Terms posted at commonpaper.com.

package/content/templates/common-paper-one-way-nda/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper One-Way NDA
+category: confidentiality
 description: >-
   A one-way (unilateral) non-disclosure agreement cover page based on Common Paper's standard terms. The Discloser
   shares confidential information with the Receiver, but not vice versa. References the Standard Terms posted at

package/content/templates/common-paper-order-form/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Order Form
+category: sales-licensing
 description: >-
   An order form template for cloud service agreements, based on Common Paper's standard form. References existing Key
   Terms and covers subscription details, fees, pilot period, payment, and professional services.

package/content/templates/common-paper-order-form-with-sla/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Order Form with SLA
+category: sales-licensing
 description: >-
   An order form template with service level agreement (SLA) provisions, based on Common Paper's standard form. Extends
   the standard order form with uptime targets, response times, and support schedules.

package/content/templates/common-paper-partnership-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Partnership Agreement
+category: deals-partnerships
 description: >-
   A partnership agreement cover page and standard terms, based on Common Paper's standard form. Covers business
   partnerships including obligations, fees, territory, liability, and data processing.

package/content/templates/common-paper-pilot-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Pilot Agreement
+category: deals-partnerships
 description: >-
   A pilot agreement cover page and standard terms, based on Common Paper's standard form. Covers trial or pilot periods
   for cloud services, including fees, support, and liability provisions.

package/content/templates/common-paper-professional-services-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Professional Services Agreement
+category: professional-services
 description: >-
   A professional services agreement with key terms, statement of work, and standard terms, based on Common Paper's
   standard form. Covers consulting and professional services engagements including deliverables, IP ownership, fees, and

package/content/templates/common-paper-software-license-agreement/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Software License Agreement
+category: sales-licensing
 description: >-
   Standard terms for a software license agreement, based on Common Paper's standard form. Provides the framework terms
   for on-premise software licensing, to be used with a separate cover page and order form.

package/content/templates/common-paper-statement-of-work/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Statement of Work
+category: professional-services
 description: >-
   A statement of work template for professional services engagements, based on Common Paper's standard form. References
   a PSA or CSA Key Terms and covers scope, deliverables, timeline, fees, and expenses.

package/content/templates/common-paper-term-sheet/metadata.yaml

@@ -1,4 +1,5 @@
 name: Common Paper Term Sheet
+category: deals-partnerships
 description: >-
   A term sheet template for outlining key business terms, based on Common Paper's standard form. A simple
   topic-and-details format for early-stage deal discussions.

package/content/templates/openagreements-employee-ip-inventions-assignment/metadata.yaml

@@ -1,4 +1,5 @@
 name: OpenAgreements Employee IP and Inventions Assignment
+category: employment
 description: >-
   Employee proprietary information and inventions assignment agreement with
   explicit prior-inventions and personal-project carveout language placeholders.

package/content/templates/openagreements-employment-confidentiality-acknowledgement/metadata.yaml

@@ -1,4 +1,5 @@
 name: OpenAgreements Employment Confidentiality Acknowledgement
+category: employment
 description: >-
   Employee confidentiality and acceptable-use acknowledgement companion for
   onboarding packets, including reporting and post-employment handling.

package/content/templates/openagreements-employment-offer-letter/metadata.yaml

@@ -1,4 +1,5 @@
 name: OpenAgreements Employment Offer Letter
+category: employment
 description: >-
   A startup-focused employment offer letter template for full-time or part-time
   hiring with compensation, equity summary, and at-will framing.