MCP.so
Sign In

Esign MCP Server

@esign-cn-open-source

Basic information

Category

Other

Transports

stdio

Author

esign-cn-open-source

Submitted by

esign-cn-open-source

About Esign MCP Server

基于 Model Context Protocol (MCP) 的 e签宝电子签署工具,支持文件上传、签署流程创建、签署状态查询等功能。

#esign#e-signature#document-signing

Esign MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "esign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-esign@{version}"
      ],
      "env": {
        "HOST": "https://openapi.esign.cn",
        "APP_ID": "Your APP ID",
        "APP_SECRET": "Your APP Secret"
      }
    }
  }
}

Esign MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Esign MCP?

Esign MCP is a Model Context Protocol server that integrates with the e签宝 (eSign) electronic signing platform, enabling file upload, signing flow creation, and signing status queries via standardized MCP tools.

How to use Esign MCP?

Configure the server by setting the environment variables HOST, APP_ID, and APP_SECRET in your MCP client’s configuration, then run npx -y mcp-server-esign@{version}. Two tools are available: create_sign_flow (upload a local file and initiate a signing flow) and query_sign_flow (check the status of a flow by its ID).

Key features of Esign MCP

  • Supports multiple file formats auto‑converted to PDF.
  • Automatically checks file processing status.
  • Logs all operations to /tmp/app.log.
  • Creates signing flows with a receiver phone number.
  • Queries signing flow details by flow ID.

Use cases of Esign MCP

  • Automate contract signing from local documents (Word, PDF, images, etc.).
  • Integrate e签宝 signing into AI‑powered workflows via MCP.
  • Monitor and verify the progress of signing processes programmatically.
  • Replace manual file conversion and upload steps in document signing pipelines.

Frequently asked questions

1

What file formats are supported?

Supported formats include PDF, Word (docx, doc, rtf), Excel (xlsx, xls), PowerPoint (pptx, ppt), WPS files (wps, et, dps), images (jpeg, jpg, png, bmp, tiff, tif, gif), and HTML (html, htm). All are automatically converted to PDF.

2

Are there any file size or name restrictions?

Yes. Total file size must not exceed 50MB and a single page must be under 20MB. File names cannot contain special characters (`/ \ : * " < > | ?`) or emoji, and the extension must match the actual file format.

3

What environments are available?

The `HOST` variable accepts three values: test environment (for development), sandbox environment, and production environment (`https://openapi.esign.cn`).

4

How does error handling work?

The tool automatically catches common errors (unsupported format, upload failure, conversion failure, flow creation failure), logs them to `/tmp/app.log`, and returns a detailed error message to the user.

5

What license does this server use?

Esign MCP is distributed under the MIT license.

Comments

More Other MCP servers