DocuSeal MCP Server

DocuSeal is an open-source DocuSign alternative for creating, filling, and signing digital documents. Starting with version 2.3.7 (released March 2026), self-hosted DocuSeal instances ship with a built-in MCP server that exposes the platform's eSignature capabilities to AI agents over HTTP, so document workflows can be driven by natural language instead of bespoke API integrations.

The server exposes a focused set of tools for the core document-signing lifecycle: searching and loading templates, creating new templates from PDF/DOCX files, sending documents to submitters for signature with prefilled fields, and searching signed or pending documents. Authentication uses a Bearer token generated in the DocuSeal admin UI under Settings > MCP Server, and the server is reachable at https://yourdomain.com/mcp on any self-hosted instance.

The integration is officially maintained by the DocuSeal team and is compatible with Claude Desktop, Cursor, VS Code, ChatGPT, and other MCP-compatible clients. DocuSeal also publishes a complementary docuseal-agent-skills repository for use with agent skill frameworks. Note: the MCP server is currently available only on the self-hosted edition, not the cloud-hosted DocuSeal product.

Tools

Prerequisites

• A self-hosted DocuSeal instance running version 2.3.7 or newer. The MCP server is not available on DocuSeal Cloud.
• Admin access to the DocuSeal instance to generate an MCP token.

Step 1: Generate an MCP token

In your self-hosted DocuSeal instance, go to Settings > MCP Server and create a new MCP token. Copy the token value.

Step 2: Configure your MCP client

Add the following to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.), replacing yourdomain.com with your DocuSeal host and YOUR_TOKEN with the token from step 1:

{
  "mcpServers": {
    "docuseal": {
      "type": "http",
      "url": "https://yourdomain.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Step 3: Restart your client

Restart your MCP client. The five DocuSeal tools (search_templates, load_template, create_template, send_documents, search_documents) will be available to the agent.

• Generate a signature-ready template from a PDF contract and immediately send it to a counterparty via a single chat instruction.
• Have an agent monitor outstanding signatures by searching for pending documents and following up with submitters.
• Automate onboarding flows where new hires receive prefilled offer letters and NDAs based on data the agent pulls from another system.
• Let support or sales reps ask an AI assistant to find the latest signed version of a customer agreement without leaving the chat.
• Build internal copilots that create, send, and track signature requests as part of larger multi-tool agent workflows.

• "Find the NDA template and send it to jane@acme.com with her name prefilled."
• "Create a new template from the attached employment agreement PDF and prepare it for two signers: employee and HR."
• "List all documents pending signature from contacts at Acme Corp."
• "Has the MSA with Globex been signed yet? If not, resend it."
• "Search for templates that include the word 'service' and show me their fields."

• Officially built and maintained by the DocuSeal team, shipped as part of the main product.
• Simple HTTP transport with Bearer token auth, easy to wire into any MCP-compatible client.
• Covers the full core eSignature lifecycle: template creation, sending, and search.
• Pairs with the separate docuseal-agent-skills repo for skill-based agent frameworks.

• Only available on self-hosted DocuSeal instances (version 2.3.7+), not on DocuSeal Cloud.
• Tool surface is intentionally small (5 tools); advanced operations like webhook management or detailed submitter editing still require the REST API.
• Requires running and maintaining a self-hosted DocuSeal deployment, including TLS for the /mcp endpoint.

• docuseal-agent-skills: DocuSeal's official agent skills package, useful when your agent platform supports skills rather than MCP HTTP servers.
• rocketify-fr/docuseal-mcp-server: A community-built stdio MCP server that wraps the DocuSeal REST API using an API key, works against DocuSeal Cloud or self-hosted.
• DocuSign and PandaDoc MCP integrations (where available) for teams already using those platforms instead of DocuSeal.