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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/caffeinebounce/docuseal-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server