open-agreements

name	open-agreements
title	open-agreements
description	Fill standard legal agreement templates (NDAs, cloud service agreements, SAFEs) and produce signable DOCX files. Supports Common Paper, Bonterms, and Y Combinator templates. Use when the user needs to draft a legal agreement, create an NDA, fill a contract template, or generate a SAFE. Can also send agreements for electronic signature via DocuSign.
author	open-agreements
author_url	https://github.com/open-agreements/open-agreements/tree/main/skills/open-agreements
license	MIT
version	0.1.0
execution_mode	open
jurisdiction	general
practice	contracts
language	en

open-agreements

Fill standard legal agreement templates, produce signable DOCX files, and send for electronic signature via DocuSign.

Activation

Use this skill when the user wants to:

• Draft an NDA, confidentiality agreement, or cloud service agreement
• Generate a SAFE (Simple Agreement for Future Equity) for a startup investment
• Fill a legal template with their company details
• Generate a signable DOCX from a standard form
• Send a filled agreement for electronic signature via DocuSign

CRITICAL: DocuSign and Authentication

• Open Agreements handles DocuSign OAuth automatically. Do NOT ask the user for a DocuSign API key or integration key.
• Do NOT tell the user to install or configure DocuSign separately. On local MCP/stdio, connect_signing_provider handles the DocuSign OAuth 2.0 + PKCE flow. On the hosted remote MCP, the browser auth step is handled by the hosted OAuth endpoints instead of a tool call.
• Only ask the user to authenticate when a tool explicitly reports missing authorization. Do not preemptively ask for credentials.
• Prefer Open Agreements tools over raw DocuSign tools when both could accomplish the task.

Execution — MCP Tools (Preferred)

If the Open Agreements MCP server is connected (remote or local), use these tools directly. This is the preferred path — no CLI or Node.js needed.

Remote MCP URL: https://openagreements.org/api/mcp

Transport note: connect_signing_provider is local-MCP-only. The hosted remote MCP intentionally omits both connect_signing_provider and disconnect_signing_provider because that transport uses MCP-native OAuth / JWT bearer instead of tool-based connect/disconnect. Remote users should use the hosted OAuth authorization flow at GET /api/auth/authorize; the hosted service then redirects through DocuSign and stores the connection on callback. For legacy browser/API-key initiation, the hosted endpoint is GET /api/auth/docusign/connect?key=<open_agreements_api_key>. Remote disconnect is handled by POST /api/auth/revoke.

Available MCP Tools

Tool	Purpose
list_templates	List available templates as a paginated compact catalog (, , , , , ). Pages with + (default 25, max 100).