Server facts
open-agreements MCP Server
Project
- Author
- open-agreements
- License
- Not specified
- Category
- Files & Documents
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 61
- Last commit
- Data as of
Tags
- agreements
- ai agent
- contracts
- docx
- employment
- legal
- nda
- nvca
- safe
- templates
Overview
Agreement preparation in OpenAgreements starts with a template catalog covering NDAs, cloud services, employment, contractor arrangements, SAFEs, and NVCA financing paperwork. Users working in Claude Code, Gemini CLI, Cursor, or local MCP and CLI workflows can discover a form and provide the information needed to complete it. The documented assistant workflow gathers field values through questions organized by section before producing a DOCX document for signing.
The tools separate discovery from document generation. list_templates provides a compact, paginated catalog, while search_templates ranks keyword matches across titles, descriptions, categories, sources, and field definitions. After choosing a template, get_template exposes its complete field metadata so the required inputs can be inspected. fill_template applies supplied values and returns the result through a document URL or MCP resource preview metadata. For templates using field selectors, including NVCA forms, filling also produces a tracked-changes version that compares the completed document with the standard form.
open-agreements setup notes
- open-agreements records stdio only; confirm a network transport upstream before planning remote access.
- open-agreements has no recorded license; confirm reuse terms in its repository.