docuseal-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@docuseal-mcp-server list my document templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
docuseal-mcp-server
MCP server for DocuSeal (self-hosted or cloud) using stdio transport.
Package name: @caffeinebounce/docuseal-mcp-server
Features
Implements these MCP tools:
Templates
list_templates— list templates (paginated)get_template— get template by IDcreate_template_from_pdf— upload PDF from file path or base64
Submissions
create_submission— create signature request from templatelist_submissions— list submissions (paginated + status filter)get_submission— get submission detailsget_submission_documents— get documents for a submission (optional local download)
Submitters
list_submitters— list submitters (optionally by submission)get_submitter— get submitter detailsupdate_submitter— update submitter fields (including reminder-style flags likesend_email)
Related MCP server: DocuSeal MCP Server
Requirements
Node.js 18+
A DocuSeal instance with API enabled
API key with required permissions
Environment Variables
DOCUSEAL_URL— base URL for DocuSeal (default:http://localhost:3030)DOCUSEAL_API_KEY— API key forX-Auth-Tokenheader (required)
Example:
export DOCUSEAL_URL="http://localhost:3030"
export DOCUSEAL_API_KEY="<your-api-key>"Install and Build
npm install
npm run buildRun
npm startOr in development:
npm run devMCP Client Configuration (example)
{
"mcpServers": {
"docuseal": {
"command": "node",
"args": ["/absolute/path/to/docuseal-mcp-server/dist/index.js"],
"env": {
"DOCUSEAL_URL": "http://localhost:3030",
"DOCUSEAL_API_KEY": "<your-api-key>"
}
}
}
}Notes
API calls use
fetchand includeX-Auth-Token.API errors include HTTP status + response body in tool output for debugging.
get_submission_documentscan optionally download returned document URLs to disk using:download: trueoptional
output_dir(default:./downloads/submission_<id>)
Available Tools
10 toolscreate_submissionB
Create a signature request from a template. Required: template_id and signers (submitters). Optional: message, send_email.
Inputs: template_id (required), signers (required), message, send_email.
create_template_from_pdfC
Upload a PDF and create a template. Provide either file_path (preferred) or file_base64. Optional: name, filename.
Inputs: name, file_path, file_base64, filename.
get_submissionC
Get full submission details by submission ID.
Inputs: submission_id (required).
get_submission_documentsB
Get submission documents. Optionally merge into one PDF and download documents locally by setting download=true.
Inputs: submission_id (required), merge, download, output_dir.
get_submitterB
Get submitter details by submitter ID.
Inputs: submitter_id (required).
get_templateC
Get a template by template ID.
Inputs: template_id (required).
list_submissionsC
List submissions with pagination and filters. Supports: status, template_id, q, archived, after, before, limit.
Inputs: template_id, status, q, slug, +5 more.
list_submittersA
List submitters. Optionally filter by submission_id. Supports pagination via limit/after/before.
Inputs: submission_id, limit, after, before.
list_templatesB
List templates with pagination. Parameters: limit (max 100), after, before, q (search), archived.
Inputs: limit, after, before, q, +1 more.
update_submitterC
Update a submitter by ID. Accepts common fields like email, phone, name, completed, send_email, send_sms, and metadata.
Inputs: submitter_id (required), email, phone, name, +5 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: create_submission, get_submission, list_submissions for submissions; create_template_from_pdf, get_template, list_templates for templates; get_submitter, list_submitters, update_submitter for submitters; and get_submission_documents for document handling. No ambiguity exists as tools do not overlap in functionality.
All tool names follow a consistent verb_noun pattern with snake_case throughout: create_submission, get_submission, list_submissions, create_template_from_pdf, get_template, list_templates, get_submitter, list_submitters, update_submitter, get_submission_documents. This predictable naming aids agent selection and understanding.
With 10 tools, the count is well-scoped for a document signing server, covering core workflows for submissions, templates, and submitters. Each tool earns its place by providing distinct operations without being excessive or insufficient for the domain.
The tool set offers strong CRUD/lifecycle coverage for submissions (create, get, list), templates (create, get, list), and submitters (get, list, update), with document retrieval. Minor gaps include no update or delete for submissions and templates, but agents can work around this, and core workflows are well-supported.
Maintenance
Related MCP Connectors
Create signing requests, check status, send reminders, and manage Aoexl templates.
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
Create documents and reusable templates, request signatures, and track approvals — for AI agents.
Get PDFs signed: prepare, send and track e-signature requests, then fetch the signed copy.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.14MIT
- AlicenseAqualityDmaintenanceEnables interaction with DocuSeal's API for managing templates, submissions, and submitters for document signing.12MIT

DocuQueue MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.28 npm1MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create and manage electronic signature documents via the ZapSign API, including sending from PDF, DOCX, URL, or template, tracking status, managing signers, templates, webhooks, background checks, and account settings.MIT