- Home
- MCP servers
- Docuseal
Docuseal
- typescript
0
GitHub Stars
typescript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"caffeinebounce-docuseal-mcp-server": {
"command": "node",
"args": [
"/absolute/path/to/docuseal-mcp-server/dist/index.js"
],
"env": {
"DOCUSEAL_URL": "http://localhost:3030",
"DOCUSEAL_API_KEY": "<your-api-key>"
}
}
}
}You deploy the Docuseal MCP Server to bridge DocuSeal’s APIs with your MCP client either as a self-hosted service or in the cloud. It exposes endpoints for templates, submissions, and submitters, and can run locally as a standard input/output (stdio) server that your MCP orchestrator can start and monitor.
How to use
To use this MCP server, run it as a local process and connect your MCP client to it via the provided stdio configuration. You will typically start the server once and reference the dist/index.js entry it uses, allowing your MCP client to perform template management, submission handling, and signer management through the familiar MCP toolset.
How to install
Prerequisites you need before installation.
Install and build the server from source.
npm install
npm run build
Run the MCP server
Start the MCP server using the runtime command shown in the configuration example. The server runs as a local stdio process and is invoked by your MCP manager.
npm start
Configure the MCP client to use the Docuseal server
In your MCP client configuration, reference the stdio server with the exact command and arguments shown. The client will launch the server as a child process and communicate through standard I/O channels.
{
"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>"
}
}
}
}
Available tools
list_templates
List templates with pagination to discover available document templates.
get_template
Retrieve a template by its ID to view metadata and fields.
create_template_from_pdf
Upload a PDF from a file path or base64 to create a new template.
create_submission
Create a signature submission based on a template.
list_submissions
List submissions with optional status filtering and pagination.
get_submission
Get detailed information for a specific submission.
get_submission_documents
Fetch documents associated with a submission; supports optional local download.
list_submitters
List submitters, optionally filtered by submission.
get_submitter
Retrieve details for a specific submitter.
update_submitter
Update submitter fields, including reminder-like flags such as send_email.