ZapSign

What ZapSign MCP server does

ZapSign MCP server gives AI agents access to the official ZapSign API through MCP. It is intended for workflows that create, send, track, and administer electronic signing requests rather than for local document processing.

The available operations cover:

• Creating signing documents from PDFs, DOCX files, URLs, or ZapSign templates
• Listing and inspecting documents, including signer activity logs
• Adding, updating, removing, and signing on behalf of signers
• Positioning signatures and attaching additional documents
• Creating, updating, and deleting DOCX templates
• Creating and deleting webhooks
• Reading account plans and users, then adding or removing account users
• Starting and reading background checks
• Listing ZapSign accounts associated with an installation

The repository describes 29 tools, with both read and write operations. Examples include listing pending documents, checking a document's signature status, and creating a document with a named signer.

How it works

ZapSign MCP server is hosted at https://api.mcp.ai/p_zapsign and communicates with clients over MCP over HTTP. An MCP-compatible client sends tool calls to that endpoint, which connects those requests to ZapSign's official API. The repository identifies Claude Desktop, Cursor, VS Code, Cline, Continue, ChatGPT, Manus, OpenClaw, and other MCP clients as supported connection targets.

The tool names distinguish resources and actions. For example, document tools provide separate operations for listing, retrieving, creating, updating, refusing, deleting, and placing signatures. Account plan and user access are exposed as separate tools, while webhook management supports creation and deletion but not listing because the ZapSign API does not provide a listing endpoint.

Setup and configuration

Generate a ZapSign API token in the ZapSign dashboard under Settings, Integrations, and ZapSign API. The hosted MCP connection can then be added using the endpoint above. The README also provides one-click or client-specific installation links for Claude, Cursor, and VS Code.

For Claude, add a custom connector with the server URL. Cursor and VS Code have dedicated installation links that configure the same HTTP endpoint. Other clients can connect if they support MCP over HTTP. The documentation also mentions magic-link login without a password as an available login method.

Tools and capabilities

The document tools support creation from source files, URLs, and templates, along with updates, refusal, deletion, signature placement, extra-document attachments, and status-related reads. Signer tools handle the people involved in a signing request, including adding, editing, removing, and completing a signature.

Template tools manage DOCX-based models. Webhook tools create and remove event callbacks. Account tools expose plan details such as credits, status, and billing period, list account users 25 at a time, and manage account users. Background-check creation is also available alongside result reads.

Limitations and notes

The hosted MCP server is proprietary. The GitHub repository is an MIT-licensed wrapper containing manifests, documentation, and skills; that license does not make the hosted service open source.

Background-check creation consumes account credits. Webhook listing is unavailable because the underlying ZapSign API has no endpoint for it. Data returned by tools is sent to the LLM host selected by the user, such as Claude, ChatGPT, Cursor, or another agent host. The repository recommends considering a host plan with training opt-out when handling this data.

ZapSign MCP server is therefore best suited to users who already have a ZapSign account and API access, and who accept the hosted MCP deployment and the data-handling path through their chosen LLM client.