DocuSeal MCP Server
Related Servers
Alternatives to DocuSeal MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityFmaintenanceEnables interaction with DocuSeal instances to manage document templates, create signature requests, and track submission statuses. It provides tools for uploading PDFs, managing submitters, and downloading signed documents via the DocuSeal API.10-
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.1431 npmMIT
- AlicenseAqualityDmaintenanceEnables managing electronic signatures and contracts through the eSignatures API, including creating, sending, and withdrawing contracts, as well as managing templates and collaborators.13MIT
- AlicenseBqualityDmaintenanceEnables interaction with the SendForSign API to list document templates and read template content for electronic signature workflows.27 npmMIT
- AlicenseAqualityBmaintenanceEnables AI clients to create and manage e-signature sessions, envelopes, documents, and webhooks through the SignDocs Brasil API.24197 npmMIT

DocuQueue MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.1MIT
TDQS
Scored across 12 tools
Each tool clearly targets a specific resource and action: templates, submissions, and submitters are all distinct, and operations like list, get, clone, archive, create, and update are unambiguous. No two tools could be easily confused.
All tools follow the pattern 'docuseal_<verb>_<noun>', with consistent snake_case and a clear verb-noun structure. The only longer name, create_template_from_pdf, still fits the pattern as a verb-noun phrase.
With 12 tools covering three main resource types (templates, submissions, submitters), the count is well within the ideal range. Each tool serves a distinct purpose without unnecessary bloat.
The core document signing workflow is covered: template creation from PDF, listing/archiving templates, creating/listing submissions, and managing submitters. Minor gaps exist like updating a template or creating/deleting submitters directly, but these are likely handled through other flows.