ZapSign

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.0Updated Oct 28, 2026

ZapSign electronic document signing via the official API: create documents for signature (from PDF,

VerifiedStreamable HTTPWeb executableProductivity & Workflow Business & Commerce

Server details

Identifier: io.github.mcp-dir/zapsign-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mcp-dir for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mcp-dir%2Fzapsign-mcp.svg)](https://sourceweft.com/mcp/io.github.mcp-dir%2Fzapsign-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server for ZapSign e-signature: create, track and manage signature documents, signers, templates, webhooks and account data.

What you can do: List and read signature documents, signer logs, signer details, templates and background checks
Create, update, delete and refuse documents, including from templates, and place signatures or attach extra documents
Add, update, remove and sign for signers, with auth modes such as email, SMS or WhatsApp tokens
Create, update and delete DOCX templates and manage webhooks
Create background checks (consuming credits) and read their status and report
Read account plan and credits, list users, and create or delete account users
When to use it: Useful when you want an assistant to prepare and send documents for electronic signature, check signing status, or manage ZapSign templates, signers and account users without leaving the chat.
Requirements: A remote MCP endpoint over HTTP; no local package. A ZapSign account and API token generated in the ZapSign panel under Settings, Integrations, ZAPSIGN API. The README describes magic-link login and an Authorization Bearer header for a permanent connection.

Before you install

Many tools write, send, or delete: documents, signers, templates, webhooks and account users, and signer emails or WhatsApp messages may be sent automatically. Background checks consume credits, and plans are paid beyond the free tier. Signer personal data and document data are returned to whichever LLM host you connect. The hosted server is proprietary.

Installation

In SourceWeft

Open ZapSign in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mcp-dir%2Fzapsign-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zapsign": {
      "type": "http",
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

README

ZapSign

ZapSign para Claude, ChatGPT e agentes de IA

Assinatura eletrônica de documentos ZapSign via API oficial: criar documentos para assinatura (de PDF, DOCX, URL ou template), acompanhar status, gerenciar signatários e autenticação, templates, webhooks, verificação de antecedentes e plano da conta. Gere seu API Token no painel em Configurações → Integrações → ZAPSIGN API.

📊 29 ferramentas
✏️ Leitura e escrita
💬 Funciona com qualquer cliente MCP: Claude Desktop, Cursor, VS Code, Cline, Continue
🔑 Login via magic-link (sem senha)

English version · Documentação completa · Skill pra agentes

Instalar em 1 clique

Claude (Web e Desktop)

A Anthropic unificou a instalação de MCPs em claude.ai/customize/connectors. O mesmo link serve pra Claude Web e Claude Desktop (basta estar logado):

➕ Abrir no Claude e conectar

Manual (se o deeplink não abrir): claude.ai/customize/connectors → + → Adicionar conector personalizado → cole Nome ZapSign e URL https://api.mcp.ai/p_zapsign.

Cursor

➕ Instalar ZapSign no Cursor

VS Code (Copilot Chat)

➕ Instalar ZapSign no VS Code

ChatGPT, Manus, OpenClaw e mais 40+ clientes

Funciona em qualquer cliente MCP que suporte MCP over HTTP. A URL do servidor é sempre:

Detalhes por cliente: INSTALL.md.

Exemplos de uso

Crie um documento para assinatura a partir deste PDF e adicione o signatário João ([email protected])Liste os documentos pendentes de assinaturaQual o status de assinatura do documento X?

Crie um documento para assinatura a partir deste PDF e adicione o signatário João ([email protected])Liste os documentos pendentes de assinaturaQual o status de assinatura do documento X?

29 ferramentas disponíveis

Tool	Descrição
`zapsign_list_accounts`	Lista contas ZapSign vinculadas a este install — id e apelido.
`zapsign_documents_list`	Documentos de assinatura no ZapSign (leitura).
`zapsign_documents_get`	Documentos de assinatura no ZapSign (leitura).
`zapsign_documents_signer_log`	Documentos de assinatura no ZapSign (leitura).
`zapsign_documents_write_create`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_create_from_template`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_update`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_delete`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_refuse`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_place_signatures`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_documents_write_add_extra_doc`	Criar/alterar documentos de assinatura no ZapSign.
`zapsign_signers_get`	Signatários no ZapSign (leitura).
`zapsign_signers_write_add`	Gerenciar signatários no ZapSign.
`zapsign_signers_write_update`	Gerenciar signatários no ZapSign.
`zapsign_signers_write_remove`	Gerenciar signatários no ZapSign.
`zapsign_signers_write_sign`	Gerenciar signatários no ZapSign.
`zapsign_templates_list`	Templates (modelos DOCX) no ZapSign (leitura).
`zapsign_templates_get`	Templates (modelos DOCX) no ZapSign (leitura).
`zapsign_templates_write_create`	Gerenciar templates no ZapSign.
`zapsign_templates_write_update`	Gerenciar templates no ZapSign.
`zapsign_templates_write_delete`	Gerenciar templates no ZapSign.
`zapsign_webhooks_write_create`	Gerenciar webhooks no ZapSign (não há endpoint de listagem na API).
`zapsign_webhooks_write_delete`	Gerenciar webhooks no ZapSign (não há endpoint de listagem na API).
`zapsign_checks_get`	Verificação de antecedentes no ZapSign (leitura).
`zapsign_checks_write_create`	Criar verificação de antecedentes no ZapSign (consome créditos).
`zapsign_account_plan`	Conta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: plan]
`zapsign_account_users`	Conta ZapSign (leitura). Ações: plan (info do plano: créditos, status, período); users (page — lista usuários da conta, 25/página). [Flattened action: users]
`zapsign_account_write_create_user`	Gerenciar usuários da conta ZapSign.
`zapsign_account_write_delete_user`	Gerenciar usuários da conta ZapSign.

Detalhe de cada tool: docs/ferramentas.md

Preços

Planos a partir do tier grátis. Veja docs/precos.md.

Privacidade & LGPD

Sub-processadores: ZapSign, o LLM host que você escolher (Claude, ChatGPT, Cursor, agente próprio). Lista completa em docs/privacidade-lgpd.md.
Os dados retornados pelas tools são enviados ao LLM host que você escolher, sub-processador fora do nosso controle. Recomendamos planos com opt-out de treinamento.

Perguntas frequentes

O servidor é open source? O servidor é proprietário (hosted). Este repositório é o wrapper público com manifestos, docs e skills — tudo MIT.

Posso usar com agente próprio (não Claude/Cursor)? Sim — qualquer cliente que suporte MCP over HTTP. URL: https://api.mcp.ai/p_zapsign.

Suporte

Licença

MIT — veja LICENSE. O servidor MCP em api.mcp.ai/p_zapsign é proprietário (hosted); este repositório (manifestos, docs, skills) é MIT.

Source: README.md at commit 2be8839

Tools

zapsign_list_accounts

Lista contas ZapSign vinculadas a este install — id e apelido.

Parametersaccount

zapsign_documents_list

Documentos de assinatura no ZapSign (leitura). Ações: list (filtros: page, status pending|signed|refused, folder_path, deleted, signer_email, created_from/created_to YYYY-MM-DD, sort_order asc|desc, include_signers); get (doc_token — detalhe + signatários + extra_docs + URLs de arquivo, que expiram em 60min); signer_log (doc_token — trilha de auditoria; download_pdf=true retorna o PDF do log). [Flattened action: list]

Parameterspagestatusaccountdeleteddoc_tokencreated_tosort_orderfolder_pathcreated_fromdownload_pdfsigner_emailinclude_signers

zapsign_documents_get

Parameterspagestatusaccountdeleteddoc_tokencreated_tosort_orderfolder_pathcreated_fromdownload_pdfsigner_emailinclude_signers

zapsign_documents_signer_log

Parameterspagestatusaccountdeleteddoc_tokencreated_tosort_orderfolder_pathcreated_fromdownload_pdfsigner_emailinclude_signers

zapsign_documents_write_create

Criar/alterar documentos de assinatura no ZapSign. Ações: - create (data): cria documento. Campos: name*, signers[]* (cada {name, email, phone_country, phone_number, auth_mode}); UMA fonte de arquivo: url_pdf | base64_pdf | url_docx | base64_docx | markdown_text; opc lang, disable_signer_emails, date_limit_to_sign, signature_order_active, folder_path, external_id. - create_from_template (data): cria via template. Campos: template_id*, signer_name*, data[]* (cada {de, para} substituindo {{VAR}}); opc signer_email, send_automatic_email, send_automatic_whatsapp, folder_path, external_id, lang. - update (doc_token, data): só com doc "em andamento". Campos: name, date_limit_to_sign, folder_path, extra_docs[]. - delete (doc_token): soft-delete. - refuse (data): cancela/recusa. Campos: doc_token*, rejected_reason*, notify_signer. - place_signatures (doc_token, data): posiciona assinaturas por coordenadas. Campo: rubricas[] ({signer_token, page 0-based, relative_position_left/bottom, relative_size_x/y, type signature|visto}). - add_extra_doc (doc_token, data): anexa PDF extra. Campos: name*, url_pdf | base64_pdf. [Flattened action: create]