docuseal-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCUSEAL_URL | No | Base URL for DocuSeal (e.g., your self-hosted instance or cloud URL) | http://localhost:3030 |
| DOCUSEAL_API_KEY | Yes | API key for X-Auth-Token header required to authenticate with DocuSeal |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesB | List templates with pagination. Parameters: limit (max 100), after, before, q (search), archived. |
| get_templateC | Get a template by template ID. |
| create_template_from_pdfC | Upload a PDF and create a template. Provide either file_path (preferred) or file_base64. Optional: name, filename. |
| create_submissionB | Create a signature request from a template. Required: template_id and signers (submitters). Optional: message, send_email. |
| list_submissionsC | List submissions with pagination and filters. Supports: status, template_id, q, archived, after, before, limit. |
| get_submissionC | Get full submission details by submission ID. |
| get_submission_documentsB | Get submission documents. Optionally merge into one PDF and download documents locally by setting download=true. |
| list_submittersA | List submitters. Optionally filter by submission_id. Supports pagination via limit/after/before. |
| get_submitterB | Get submitter details by submitter ID. |
| update_submitterC | Update a submitter by ID. Accepts common fields like email, phone, name, completed, send_email, send_sms, and metadata. |
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 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.