A
licenseA
qualityD
maintenanceEnables interaction with DocuSeal's API for managing templates, submissions, and submitters for document signing.
12
10 npm
MIT
docuseal-mcp-server
Related Servers
Alternatives to docuseal-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.1454 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
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- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create branded documents from templates and data, send them for acceptance or signature, and track their status and recipients.MIT
documenteroofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to list Documentero templates, inspect their field schemas, and generate Word/PDF/Excel documents via the Documentero API.37 npm1MIT
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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
ActivityInactive
ResponsivenessNo issues