eSignatures

Exposes contract and template management through the Model Context Protocol (MCP) standard, enabling LLM agents and tools to programmatically create, retrieve, update, and delete contract templates via standardized JSON-RPC 2.0 message handlers. Implements resource-based routing with typed input/output schemas that allow AI systems to understand available operations and their parameters without custom integration code.

Provides create, read, update, and delete operations for contract templates with support for dynamic variable substitution and placeholder management. Templates are stored with metadata (name, description, signatories) and can be retrieved individually or listed with filtering, enabling reusable contract patterns that adapt to different parties and terms via variable binding at execution time.

Enables LLM agents to draft contracts by combining template selection, variable binding, and content generation within a single MCP workflow. The agent can request a template, populate variables based on party information, and optionally generate missing clauses or terms using the LLM's reasoning capabilities, producing a complete contract ready for review or signature.

Orchestrates multi-party contract review workflows by managing contract state transitions (draft → review → approved → signed) and tracking reviewer feedback through MCP operations. Enables agents to route contracts to appropriate reviewers, collect comments, and coordinate approval decisions without direct database access — all state changes flow through MCP endpoints with audit trails.

Integrates with eSignatures backend to send contracts for signature collection, managing signer lists, signature workflows, and completion tracking through MCP endpoints. Agents can initiate signature requests, specify signer order and authentication requirements, and poll for completion status — the MCP server handles the underlying eSignatures API communication and webhook processing.

Retrieves signed or draft contracts in multiple formats (PDF, HTML, plain text) through MCP endpoints, enabling agents to access contract content for analysis, archival, or downstream processing. Supports filtering by contract ID, status, date range, and party information — the server handles format conversion and document generation without exposing file system details.

Provides read-only MCP endpoints for querying contract metadata (creation date, parties, status, version history) and audit logs (state transitions, reviewer actions, signature events) without exposing raw database queries. Agents can search contracts by party name, date range, or status, and retrieve complete audit trails for compliance and dispute resolution purposes.

Coordinates contract negotiation workflows where multiple parties propose amendments, counter-offers, or revisions through MCP endpoints. Agents can track proposed changes, merge compatible amendments, flag conflicts, and route counter-proposals back to relevant parties — the server maintains version history and change tracking without requiring manual diff management.