SignNow

You can run the SignNow MCP Server to grant AI agents secure, structured access to SignNow eSignature workflows. It supports templates, embedded signing, invites, status tracking, and document downloads over STDIO for local clients or Streamable HTTP for remote or containerized setups. This enables you to automate signing workflows from AI-enabled tools and applications.

How to use

Start by choosing how you want to run the MCP server: STDIO for local development or HTTP for remote usage. Connect your MCP client to one of the provided endpoints, and then use the available tools to list templates, create documents from templates, invite signers, and retrieve final documents. Begin with exploring templates, then create from a template, and proceed to embedded signing or sending as needed. Use the inspector or tool schemas in your client to understand the exact inputs for each action.

How to install

Prerequisites You need a SignNow account and a SignNow API application. You will also require Python 3.11 or newer and optionally UVX for rapid setup.

Install from PyPI and run in standalone STDIO mode (local development):

pip install signnow-mcp-server
sn-mcp serve

Install from source for development and run in STDIO mode:

git clone https://github.com/signnow/sn-mcp-server.git
cd sn-mcp-server
cp .env.example .env
# fill in your values in .env

pip install -e .

sn-mcp serve

Run the HTTP server for remote access (default port 8000):

sn-mcp http

Or customize host/port and enable reload during development:

sn-mcp http --host 0.0.0.0 --port 8000 sn-mcp http --reload

## Additional sections

Configuration covers authentication, API endpoints, and production key management. You can use username/password or OAuth 2.0 to authenticate. If you enable OAuth, provide RSA private keys for token signing and configure issuer and redirects accordingly.

Security and production readiness tips include using a persistent RSA private key, managing keys via secrets, and selecting the appropriate transport (STDIO for local testing, HTTP for containers or remote deployments).

Examples and resources are provided for various client integrations and testing workflows. You can explore sample apps and API helper tools to accelerate integration with SignNow capabilities.

## Available tools

### list\_all\_templates

List all templates and template groups with simplified metadata.

### list\_documents

Browse documents, document groups, and their statuses.

### create\_from\_template

Create a document or a group from a template or template group.

### send\_invite

Send email invites for documents or groups, with ordered recipients.

### create\_embedded\_invite

Create an embedded signing session without email delivery.

### create\_embedded\_sending

Create an embedded sending/management experience.

### create\_embedded\_editor

Create an embedded editor link to adjust fields on a document.

### send\_invite\_from\_template

One-shot: create from a template and invite.

### create\_embedded\_sending\_from\_template

One-shot: template to embedded sending.

### create\_embedded\_editor\_from\_template

One-shot: template to embedded editor.

### create\_embedded\_invite\_from\_template

One-shot: template to embedded signing.

### get\_invite\_status

Check current invite status and step details.

### get\_document\_download\_link

Provide a direct download link for merged outputs.

### get\_signing\_link

Obtain a signing link for a document or group.

### get\_document

Retrieve the normalized document or group structure with field values.

### update\_document\_fields

Prefill text fields in documents.