4,000+ servers built on MCP Fusion
Vinkius
CrewAIFramework
Why use HotDocs MCP Server with CrewAI?

Bring Document Automation
to CrewAI

Create your Vinkius account to connect HotDocs to CrewAI and start using all 14 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Complete AssemblyCreate Interview SessionCreate Work ItemGet Auth TokenGet Document ContentGet Template PackageGet Unanswered VariablesGet Work ItemList DocumentsList Template PackagesList Template VersionsList Work ItemsList Work Items By DateUpdate Answers
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
HotDocs

What is the HotDocs MCP Server?

Connect your HotDocs Advance tenancy to any AI agent and take full control of your document automation workflows through natural conversation.

What you can do

  • Template Discovery — List all template packages and their versions available in your HotDocs tenancy
  • Work Item Management — Create, inspect, and manage work items that hold interview data and assembled documents
  • Interview Sessions — Initialize interview sessions programmatically for interactive data collection
  • Automated Document Assembly — Inject answers via XML and trigger document generation without manual UI interaction
  • Document Retrieval — List and download assembled documents (PDFs, Word docs) directly from the agent
  • Validation & Auditing — Check unanswered variables, list work items by date range or user, and audit assembly history

How it works

  1. Subscribe to this server
  2. Enter your HotDocs Advance tenancy, API client name, service principal name, and password
  3. Start automating your document workflows from Claude, Cursor, or any MCP-compatible client

No more repetitive clicking through the HotDocs web interface. Your AI acts as a dedicated document automation specialist.

Who is this for?

  • Legal Teams — instantly generate contracts, agreements, and legal forms by providing case details in natural language
  • HR Departments — automate offer letters, employment contracts, and policy documents at scale
  • Financial Services — assemble loan applications, compliance forms, and client onboarding documents rapidly
  • Operations & Compliance — batch-generate standardized documents and audit interview completeness across teams

Built-in capabilities (14)

complete_assembly

This processes all collected answers and assembles the final documents based on the template configuration. After calling this, the assembled documents become available for download via list_documents and get_document_content. You must have already created a work item, created a version/session, and provided answers (via interview or update_answers). The workItemId and versionId must match an existing work item and its version. Complete document assembly for a work item version

create_interview_session

This endpoint prepares the system to collect answers for the template variables. The response contains interview data needed to render the HotDocs interview UI. Use this before displaying the interview to the user or before assembling documents. The versionId should be unique for each interview session (e.g., v1, v2, or a UUID). Create a new interview session for a work item

create_work_item

A work item is associated with a specific template package and holds answers provided during interviews. You must provide a unique workItemId (alphanumeric identifier you choose) and optionally a templatePackageId. The workItemId becomes the reference for all subsequent operations (interview, assembly, download). IMPORTANT: workItemId must be unique and URL-safe (letters, numbers, hyphens only). Create a new work item in HotDocs Advance

get_auth_token

This is primarily a utility function for debugging authentication issues. The token is used internally by all other tools automatically. If other tools fail with auth errors, verify your credentials are correct. Get a fresh HotDocs API access token

get_document_content

Use this to download the final generated document (PDF, Word, etc.) after assembly is complete. You need the workItemId and the documentId (obtained from list_documents). The response includes the document content and a download URL for direct access. Download/get content of an assembled document

get_template_package

Use the template package ID obtained from list_template_packages. This helps understand the template structure before creating work items. Get details of a specific template package

get_unanswered_variables

This shows which template variables were not provided answers during the interview process. Useful for validating interview completeness before or after document assembly. Requires the workItemId and documentId (from list_documents). The response includes the list of unanswered variables and assembly results. Get unanswered variables from an assembled document

get_work_item

Use this to inspect a work item before or after conducting interviews or assembling documents. The workItemId is the unique identifier you assigned when creating the work item. Get details of a specific work item

list_documents

After completing assembly, this shows all generated documents with their IDs, names, and metadata. Use the document IDs returned here to download individual documents via get_document_content. Each document entry includes filename, creation date, and assembly results information. List all assembled documents for a work item

list_template_packages

Template packages define the structure of documents that can be assembled. Each package contains interview questions and document output configurations. Use this to discover what templates are available for document assembly. The response includes package IDs which are required for creating work items. List all available template packages in HotDocs Advance

list_template_versions

Each template can have multiple versions over time. This shows version history and helps identify which version is currently live/active. Use the package_id from list_template_packages to query versions. List all versions of a template package

list_work_items

You can filter by user ID and/or date range to find specific work items. Leave all parameters empty to list all work items. This is useful for auditing, tracking progress, or finding existing work items to continue working on. Date format should be ISO 8601 (e.g., 2024-01-15 or 2024-01-15T10:30:00). List work items with optional filters

list_work_items_by_date

This is optimized for date-based filtering and auditing. Both fromDate and toDate are required for this tool. Use ISO 8601 date format (e.g., 2024-01-01 or 2024-01-01T00:00:00 for datetime). This is useful for generating reports on document assembly activity over time periods. List work items filtered by a specific date range

update_answers

The answer_xml parameter must contain valid HotDocs answer XML format that matches the template variables. This is useful for automated/batch document assembly where you already have the data. You can call this multiple times to incrementally add answers. Answer XML format example: <AnswerSet><A v="VariableName"><V>Answer Value</V></A></AnswerSet> Update answers for a work item using XML answer format

Why CrewAI?

When paired with CrewAI, HotDocs becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HotDocs tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

HotDocs in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run HotDocs with Vinkius?

The HotDocs connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 14 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

HotDocs
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect HotDocs using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

HotDocs and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect HotDocs to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures HotDocs for CrewAI

Every request between CrewAI and HotDocs is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

What credentials do I need to connect HotDocs Advance to this MCP server?

You need four pieces of information: (1) your Tenancy Moniker (the subdomain in your HotDocs URL, e.g., 'mycompany' from mycompany.hotdocsadvance.com), (2) the API Client Display Name you created in Manage API Credentials, (3) the Service Principal Name you added to that client, and (4) the Service Principal Password (which is shown only once during creation). All of these are obtained from the HotDocs Advance Auth portal.

02

Can I assemble documents automatically without going through the interview UI?

Yes! Use the create_work_item tool to initialize a work item, then use update_answers to inject your data as HotDocs answer XML, and finally call complete_assembly to trigger document generation. This fully automated bypasses the interactive interview UI entirely, perfect for batch processing or integrating with external data sources.

03

How do I find and download documents that have already been assembled?

Use the list_documents tool with your workItemId to see all assembled documents and their IDs. Then use get_document_content with the workItemId and documentId to retrieve the actual file content. The response includes both the raw content and a direct download URL for easy access to your PDFs or Word documents.

04

What is a work item and why is it important?

A work item is a unique container in HotDocs Advance that holds interview answers, template associations, and assembled documents for a specific case. Think of it as a 'file folder' for each document automation request. It's identified by a unique ID you assign (like 'contract-john-doe-2024') and persists all data so you can revisit, update, and reassemble documents at any time.

05

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

06

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

07

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

08

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

09

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

10

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

11

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

12

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

13

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →