Skip to main content
Glama

docuseal-mcp-server

MCP server for DocuSeal (self-hosted or cloud) using stdio transport.

Package name: @caffeinebounce/docuseal-mcp-server

Features

Implements these MCP tools:

Templates

  • list_templates — list templates (paginated)

  • get_template — get template by ID

  • create_template_from_pdf — upload PDF from file path or base64

Submissions

  • create_submission — create signature request from template

  • list_submissions — list submissions (paginated + status filter)

  • get_submission — get submission details

  • get_submission_documents — get documents for a submission (optional local download)

Submitters

  • list_submitters — list submitters (optionally by submission)

  • get_submitter — get submitter details

  • update_submitter — update submitter fields (including reminder-style flags like send_email)

Related MCP server: DocuSeal MCP Server

Requirements

  • Node.js 18+

  • A DocuSeal instance with API enabled

  • API key with required permissions

Environment Variables

  • DOCUSEAL_URL — base URL for DocuSeal (default: http://localhost:3030)

  • DOCUSEAL_API_KEY — API key for X-Auth-Token header (required)

Example:

export DOCUSEAL_URL="http://localhost:3030"
export DOCUSEAL_API_KEY="<your-api-key>"

Install and Build

npm install
npm run build

Run

npm start

Or in development:

npm run dev

MCP Client Configuration (example)

{
  "mcpServers": {
    "docuseal": {
      "command": "node",
      "args": ["/absolute/path/to/docuseal-mcp-server/dist/index.js"],
      "env": {
        "DOCUSEAL_URL": "http://localhost:3030",
        "DOCUSEAL_API_KEY": "<your-api-key>"
      }
    }
  }
}

Notes

  • API calls use fetch and include X-Auth-Token.

  • API errors include HTTP status + response body in tool output for debugging.

  • get_submission_documents can optionally download returned document URLs to disk using:

    • download: true

    • optional output_dir (default: ./downloads/submission_<id>)

Available Tools

10 tools
create_submissionB

Create a signature request from a template. Required: template_id and signers (submitters). Optional: message, send_email.

Inputs: template_id (required), signers (required), message, send_email.

create_template_from_pdfC

Upload a PDF and create a template. Provide either file_path (preferred) or file_base64. Optional: name, filename.

Inputs: name, file_path, file_base64, filename.

get_submissionC

Get full submission details by submission ID.

Inputs: submission_id (required).

get_submission_documentsB

Get submission documents. Optionally merge into one PDF and download documents locally by setting download=true.

Inputs: submission_id (required), merge, download, output_dir.

get_submitterB

Get submitter details by submitter ID.

Inputs: submitter_id (required).

get_templateC

Get a template by template ID.

Inputs: template_id (required).

list_submissionsC

List submissions with pagination and filters. Supports: status, template_id, q, archived, after, before, limit.

Inputs: template_id, status, q, slug, +5 more.

list_submittersA

List submitters. Optionally filter by submission_id. Supports pagination via limit/after/before.

Inputs: submission_id, limit, after, before.

list_templatesB

List templates with pagination. Parameters: limit (max 100), after, before, q (search), archived.

Inputs: limit, after, before, q, +1 more.

update_submitterC

Update a submitter by ID. Accepts common fields like email, phone, name, completed, send_email, send_sms, and metadata.

Inputs: submitter_id (required), email, phone, name, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.
      28 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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