HotDocs MCP for AI Agents. Automate Contract and Compliance Document Assembly
HotDocs MCP automates complex document assembly workflows by connecting your favorite AI agent directly to template libraries. It lets you create work items, conduct virtual interviews to gather required data, and generate finalized legal documents—like contracts or compliance reports—without ever touching the web interface.
Give Claude and any AI agent real-world access
List all template packages and check version history to find exactly which document structure you need.
Create, inspect, and update work items—the digital records that hold the data for an assembly job.
Initialize interactive sessions to programmatically collect specific answers required by a template before generation.
Inject collected data and trigger the final assembly process to generate ready-to-download documents.
Check which required variables were left unanswered or retrieve a complete history of document attempts for compliance checks.
Ask an AI about this
Waiting for input…
What AI agents can do with HotDocs - 14 Tools for Document Automation
These tools allow you to programmatically manage every step of the document lifecycle: discovering templates, gathering answers, assembling files, and auditing results.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using HotDocs MCPComplete Assembly
Runs the final process, taking all collected answers and building the full document based on the template's rules.
Create Interview Session
Prepares the system by setting up a unique session to collect structured answers for...
Create Work Item
Establishes a new record identifier, which acts as the single reference point for...
Get Auth Token
Retrieves a fresh API access token. Use this if any other tool fails due to...
Get Document Content
Downloads the finished document content, providing both the file and a direct URL...
Get Template Package
Fetches detailed information about a specific template package ID to understand its structure before building a record.
Get Unanswered Variables
Checks an assembled document and reports any variables that were not provided answers, helping you validate completeness.
Get Work Item
Retrieves the full details of a specific work item at any point—before or after...
List Documents
Lists all generated documents for a given work item, providing their IDs and...
List Template Versions
Shows the historical versions of a template package, helping you know which version...
List Template Packages
Lists every available document template package in your tenancy so you can discover...
List Work Items By Date
Finds specific records by filtering them using a defined start and end date range, useful for reporting.
List Work Items
Searches for work items using optional filters like user ID or a general date range to locate existing jobs.
Update Answers
Allows you to batch-feed data into an existing record using XML format, ideal when...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with HotDocs, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by HotDocs Advance. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The manual cycle of document creation is exhausting. Solved with Vinkius AI Gateway
Right now, generating a single client agreement means jumping between tabs. You have to copy the client name from one place into another, fill in dates on a separate form, and then cross-reference details across three different documents just to make sure you didn't miss anything. Then, you download all those PDFs and manually check that every variable is filled.
With this MCP, your agent handles the whole thing conversationally. You tell it what you need; it guides the data gathering process, injects everything into the right template, runs the assembly engine in the background, and gives you a single, final document ready to send out.
HotDocs MCP: Automated Document Assembly
The biggest manual steps that disappear are the repetitive data entry and the cross-checking phase. You never have to manually track down which variables were missed or worry about making sure the correct document version is used for a specific client type.
What changes now is control. Instead of being limited by a browser interface, you programmatically manage the entire document lifecycle—from template discovery right through to final file retrieval.
What your AI can actually do with this
Document creation shouldn't feel like filling out 17 separate forms in a browser. This MCP gives your AI client full control over document assembly using HotDocs Advance templates. You can tell your agent, 'Generate a new employment contract for Jane Doe,' and it handles everything after that.
Your agent first discovers the necessary template packages. It then creates a work item to track the process and initiates an interview session so you can answer questions conversationally. Once all data is collected, the system runs the final assembly, injecting all your answers into the correct document variables and generating files like PDFs or Word documents.
You don't just get a file; you get auditable proof of what information was captured along the way.
If you're building out an enterprise process—say, onboarding new clients or handling compliance audits—this MCP provides the necessary structure to make that happen programmatically. It’s one of the most powerful document automation tools available in the Vinkius catalog because it lets your AI act like a dedicated specialist, managing data flow and generation through natural conversation.
019d75b3-41ea-7194-81dc-117284079a8b Here's how it actually works
The bottom line is that your AI client manages the entire multi-step process—from initial data gathering to final download—in a single conversation flow.
First, ask your agent to use the list_template_packages tool to see what template structures are available.
Next, have your agent create a new record using create_work_item, then run create_interview_session to gather all necessary data points from you or an external source.
Finally, trigger the generation by calling complete_assembly, and retrieve the finished file content using get_document_content.
Who is this actually for?
Anyone whose job involves turning variable data into standardized, legally sound documents. This MCP saves time for legal and compliance teams who spend hours clicking through forms and manually compiling reports.
Writing contracts or NDAs by having the agent populate templates with case details and then downloading the finalized, signed-ready PDF.
Automating bulk document generation for new hires, like offer letters or policy acknowledgments, while tracking which records are missing required data points.
Running audits by listing work items over a date range and checking them specifically for unanswered variables to prove due diligence was performed.
What Changes When You Connect
Stop copy-pasting data across multiple forms. By using the create_interview_session tool, your agent captures necessary inputs through natural conversation, building a complete record before generation.
Eliminate manual document retrieval. After running complete_assembly, you can immediately use list_documents and then get_document_content to download the final file without clicking anything in the UI.
Prove compliance easily. Use get_unanswered_variables on any assembly record to instantly check if a document is missing critical fields, giving you an auditable checklist of incomplete records.
Improve data tracking across teams. Instead of relying on shared spreadsheets, use list_work_items_by_date and list_work_items to create a single source of truth for all document activity over time.
Handle complex inputs batch-wise. If you have 50 records ready but no interview flow, simply call update_answers with XML data to bypass the conversational stage entirely.
See it in action
Onboarding a new employee
The HR agent needs three documents: contract, benefits guide, and tax form. It starts by listing all template packages (list_template_packages), then creates the work item and runs create_interview_session to gather salary and start dates. Finally, it calls complete_assembly to generate all three branded files.
Handling a legal discovery request
A compliance analyst needs to find every document related to 'Project X' created last quarter. The agent uses list_work_items_by_date and filters by user ID, then checks the resulting records with get_unanswered_variables to flag any potential gaps in documentation.
Processing client loan applications
The finance team has 100 completed application forms saved as data files. Instead of manually entering the details, the agent uses update_answers with a batch XML dump for all 100 records, then runs complete_assembly to generate 100 final loan agreements.
Auditing document completeness
A manager wants to review the last month's contract signings. They use list_work_items by date, then for each item, they check with get_unanswered_variables. This instantly highlights if any required fields were missed during the interview process.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to download before assembly
The user calls list_documents and immediately tries to use get_document_content on a document ID, expecting the final file. This fails because the data hasn't been injected yet.
Always run complete_assembly first. That process takes all gathered answers and generates the file structure. Only after that can you trust the IDs returned by list_documents for use with get_document_content.
Using wrong work item identifiers
The user tries to run get_work_item using a generic name or an ID that doesn't match the unique alphanumeric identifier they assigned during creation. The tool returns a 'not found' error.
Remember, when you call create_work_item, you must choose and use that specific, unique workItemId for every subsequent operation (like get_work_item or create_interview_session). It’s the record's primary key.
Ignoring data source formats
The user tries to update answers by pasting plain text into a tool, without wrapping it in the required XML structure. The process fails because the template requires specific variable tags.
When using update_answers, you must format your input as valid HotDocs Answer XML (e.g., <AnswerSet><A v="VariableName"><V>Answer Value</V></A></AnswerSet>). This structure tells the system exactly where the data goes.
When It Fits, When It Doesn't
Use this MCP if your process requires turning variable inputs into a single, structured output document (like a contract or compliance form). If you need to manage multiple steps—data collection, transformation, and final file creation—this is what you want. Don't use it if you are just trying to fill out one simple, fixed-field web form; those might be better handled by dedicated API connectors. If your goal is purely data auditing without generating documents, using list_work_items or get_work_item is enough. But the moment you need the system to assemble and generate a branded file based on complex logic, this MCP is necessary.
Questions you might have
How do I find out what templates are available using HotDocs MCP? +
You use list_template_packages first. This tool gives you a master list of all template packages and their unique IDs, so you know exactly which document structure to work with.
Do I have to fill out the interview manually every time with HotDocs MCP? +
No. While create_interview_session starts a conversational flow, if you already have the data (like from a CRM), you can skip that step and use update_answers with XML directly.
Can I check for incomplete contracts using HotDocs MCP? +
Yes. After an assembly attempt, run get_unanswered_variables. This tells you exactly which required fields were missed, making your compliance audits much faster and more accurate.
What if I need to download the document content after using HotDocs MCP? +
You first call list_documents to get the unique document ID. Then, pass that ID along with the workItemId into get_document_content to retrieve the file.
Does HotDocs MCP handle multiple versions of a template? +
Yes. Use list_template_versions. This allows you to check the version history for any template package, ensuring you are always using the most current or required format.