DocuSeal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCUSEAL_API_KEY | Yes | Your DocuSeal API key. Obtain from https://console.docuseal.com/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docuseal_list_templatesB | List all document templates from DocuSeal |
| docuseal_get_templateB | Get detailed information about a specific template |
| docuseal_clone_templateB | Clone an existing template into a new template |
| docuseal_archive_templateA | Archive (soft delete) a template |
| docuseal_create_template_from_pdfB | Create a template from an existing PDF with form fields |
| docuseal_list_submissionsB | List all submissions with optional filtering |
| docuseal_get_submissionB | Get detailed information about a specific submission |
| docuseal_create_submissionB | Create a new submission for document signing |
| docuseal_archive_submissionA | Archive (soft delete) a submission |
| docuseal_list_submittersB | List all submitters with optional filtering |
| docuseal_get_submitterC | Get detailed information about a specific submitter |
| docuseal_update_submitterB | Update submitter details, field values, and re-send emails |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.