SSyncDev

ZapSign (unofficial) MCP Server

ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.

Local serverstdio

What is the ZapSign (unofficial) MCP Server?

ZapSign (unofficial) is an MCP integration. ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.

Packages and local setup

The published npm package is zapsign-mcp, version 1.0.1. Its declared MCP transport is stdio.

The package declares ZAPSIGN_SANDBOX_TOKEN: API token for sandbox. On macOS it can live in the Keychain instead (see the README).; ZAPSIGN_PROD_TOKEN: API token for production. On macOS it can live in the Keychain instead (see the README)..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.0.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related e-signatures & agreements MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
ZAPSIGN_SANDBOX_TOKENAPI token for sandbox. On macOS it can live in the Keychain instead (see the README).Check documentation
ZAPSIGN_PROD_TOKENAPI token for production. On macOS it can live in the Keychain instead (see the README).Check documentation