ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.
Connect Runs on your machine
claude mcp add zapsign-mcp -e ZAPSIGN_SANDBOX_TOKEN=<ZAPSIGN_SANDBOX_TOKEN> -e ZAPSIGN_PROD_TOKEN=<ZAPSIGN_PROD_TOKEN> -- npx -y [email protected]
{
"mcpServers": {
"zapsign-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
"ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
}
}
}
}
{
"mcpServers": {
"zapsign-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
"ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
}
}
}
}
{
"servers": {
"zapsign-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
"ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ZAPSIGN_SANDBOX_TOKENOptional, secret | API token for sandbox. On macOS it can live in the Keychain instead (see the README). |
ZAPSIGN_PROD_TOKENOptional, secret | API token for production. On macOS it can live in the Keychain instead (see the README). |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 16 Oct 2026 |
| Last updated | 16 Oct 2026 |
| Registry name | io.github.BlancasJ/zapsign-mcp |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
