# ZapSign (unofficial)

> ZapSign (unofficial) is an open-source MCP server for files and documents. Unofficial ZapSign e-signature server that asks before writes and filters personal data. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI
- **Repository:** https://github.com/blancasj/zapsign-mcp
- **MCP Registry name:** io.github.BlancasJ/zapsign-mcp
- **Categories:** [files and documents](https://ai-powered.com/categories/files-and-documents), [legal and government](https://ai-powered.com/categories/legal-and-government)
- **Listing updated:** 2026-11-18

## About

This is a community-built server for the ZapSign API, designed so an agent can help with e-signature workflows without being handed signers' personal data. It is not affiliated with ZapSign, which publishes its own MCP server.

It exposes 48 tools covering documents, signers, templates, webhooks, users, plan information, background checks and partner accounts. Reads run freely; every tool that changes something carries a mark that makes Claude Code ask first, and clients that do not honour it are offered reads only. The production server offers no write tools at all, while the sandbox server has them all.

What the model sees is a filtered copy of each answer: names, emails, document numbers, states and dates pass, while CPF, CNPJ, RFC, CURP, birth dates, photos, signing links, IP addresses, location, phone fields, form answers and background-check findings are hidden. The full answer is kept in a local log the agent is not told the location of. It needs Node 22, a ZapSign API token per environment, and the README recommends settings and sandbox rules to keep the agent away from the log.

## Features

- **Write approval:** Every changing tool prompts before it runs in Claude Code.
- **Read-only production:** The prod server exposes no write tools.
- **PII filtering:** Tax IDs, birth dates, photos, signing links and IPs are hidden from the model.
- **Local full log:** Unfiltered answers are stored locally, outside the agent's reach.
- **48 API tools:** Documents, signers, templates, webhooks, plan and background checks.
- **Keychain tokens:** On macOS tokens can live in the Keychain instead of config.

## Good for

- Test a signature flow safely in the ZapSign sandbox
- List documents and check signer status in production read-only
- Audit a document's signature trail without exposing personal data
- Create a template and webhook in the sandbox

## Install

### Claude Code (Terminal)

```sh
claude mcp add zapsign-mcp --env ZAPSIGN_SANDBOX_TOKEN='<ZAPSIGN_SANDBOX_TOKEN>' --env ZAPSIGN_PROD_TOKEN='<ZAPSIGN_PROD_TOKEN>' -- npx -y zapsign-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ],
      "env": {
        "ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
        "ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ],
      "env": {
        "ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
        "ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "zapsign-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ],
      "env": {
        "ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
        "ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ],
      "env": {
        "ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
        "ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "zapsign-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zapsign-mcp"
      ],
      "env": {
        "ZAPSIGN_SANDBOX_TOKEN": "<ZAPSIGN_SANDBOX_TOKEN>",
        "ZAPSIGN_PROD_TOKEN": "<ZAPSIGN_PROD_TOKEN>"
      }
    }
  }
}
```

## Tools

- `get_document`: Get a document.
- `list_documents`: List documents.
- `get_document_audit_trail`: Get a document's signer log.
- `get_signer`: Get a signer.
- `get_signer_validations`: Get signer verification details.
- `list_templates`: List templates.
- `get_template`: Get a template.
- `get_plan`: Get plan information.
- `list_users`: List users.
- `get_background_check`: Get a background check.

## FAQ

### Is it official?

No. It is not affiliated with ZapSign, which has its own MCP server.

### Can it change production data?

No. The production server offers no write tools.

### What personal data does the model see?

Names, emails, document numbers, states and dates. Tax IDs, birth dates, photos, signing links and IPs are hidden.

### What is required?

Node.js 22 or newer and a ZapSign API token for each environment.

### Is ZapSign (unofficial) free?

Yes. ZapSign (unofficial) is open source, so you can use and self-host it for free.

### How do I add ZapSign (unofficial) to Claude Code?

Run this command in your terminal: claude mcp add zapsign-mcp --env ZAPSIGN_SANDBOX_TOKEN='<ZAPSIGN_SANDBOX_TOKEN>' --env ZAPSIGN_PROD_TOKEN='<ZAPSIGN_PROD_TOKEN>' -- npx -y zapsign-mcp

### What are the best alternatives to ZapSign (unofficial)?

The closest alternatives to ZapSign (unofficial) are SSRS2, Csv, Datos Cl, Data Ny and Cipo.

## Where this comes from

- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [SSRS2](https://ai-powered.com/mcp/ssrs2): SSRS2 is an MCP server for files and documents.
- [Csv](https://ai-powered.com/mcp/csv): Csv is a freemium MCP server for files and documents.
- [Datos Cl](https://ai-powered.com/mcp/datos-cl): Datos Cl is a freemium MCP server for legal and government.
- [Data Ny](https://ai-powered.com/mcp/data-ny): Data Ny is a freemium MCP server for legal and government.
- [Cipo](https://ai-powered.com/mcp/cipo): Cipo is a freemium MCP server for legal and government.
- [Data Europa](https://ai-powered.com/mcp/data-europa): Data Europa is a freemium MCP server for legal and government.
- [Data Govt Nz](https://ai-powered.com/mcp/data-govt-nz): Data Govt Nz is a freemium MCP server for legal and government.
- [Data Cityofchicago](https://ai-powered.com/mcp/data-cityofchicago): Data Cityofchicago is a freemium MCP server for legal and government.

---
Source: https://ai-powered.com/mcp/zapsign-unofficial
