ZapSign MCP Server

by mcp-dir Your server? Claim it

answering

ZapSign is answering right now. Last checked 1 min ago. It exposes 35 tools. Last commit 21 Aug 2026.

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

Uptime history 28 days of history · worst day 98%

28 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

1090 ms

Response time

average over 24h

Stars

last commit 21 Aug 2026

What changed 64

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 August 2026. No other catalogue keeps this.

13 Sep a tool changed version2 times that day

9 Sep a tool changed version

8 Sep a tool changed version

7 Sep a tool changed version

6 Sep a tool changed version

5 Sep a tool changed version

4 Sep a tool changed version

3 Sep a tool changed version3 times that day

2 Sep a tool changed version6 times that day

1 Sep a tool changed version2 times that day

and 54 more, back to 22 August 2026

ZapSign does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add zapsign-mcp --transport http https://api.mcp.ai/p_zapsign

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "zapsign-mcp": {
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

~/.codex/config.toml

[mcp_servers.zapsign-mcp]
url = "https://api.mcp.ai/p_zapsign"

.cursor/mcp.json

{
  "mcpServers": {
    "zapsign-mcp": {
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "zapsign-mcp": {
      "url": "https://api.mcp.ai/p_zapsign"
    }
  }
}

Available tools 35

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

zapsign

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. Ações: - create_user (data): adiciona usuário. Campos: email*; opc role (member|admin|self_docs_limited), first_name, last_name, phone_country, phone_number. - delete_user (email): remove usuário (donos não podem ser removidos). [Flattened action: create_user]

zapsign_account_write_delete_user

zapsign_checks_get

Verificação de antecedentes no ZapSign (leitura). Ação: get (check_id — status not_started|in_progress|delayed|error|completed + pdf_report). [Flattened action: get] Bulk support: accepts check_ids for batched execution.

zapsign_checks_write_create

Criar verificação de antecedentes no ZapSign (consome créditos). Ação: create (data). Campos: country* (BR|CO|CL|MX|PE), type* (ex.: person | credit_person_br), user_authorized: true*, e um identificador: national_id | foreign_id. [Flattened action: create]

zapsign_documents_get

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: get]

zapsign_documents_list

zapsign_documents_signer_log

zapsign_documents_write_add_extra_doc

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: add_extra_doc]

zapsign_documents_write_create

zapsign_documents_write_create_from_template

zapsign_documents_write_delete

zapsign_documents_write_place_signatures

zapsign_documents_write_refuse

zapsign_documents_write_update

zapsign_list_accounts

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

zapsign_signers_get

Signatários no ZapSign (leitura). Ação: get (signer_token — status, sign_url, visualizações, geo, auth_mode etc.). [Flattened action: get]

zapsign_signers_write_add

Gerenciar signatários no ZapSign. Ações: - add (doc_token, data): adiciona signatário. Campos: name*, email*; opc phone_country, phone_number, auth_mode (assinaturaTela|tokenEmail|tokenSms|tokenWhatsapp), lock_name/email/phone, qualification, send_automatic_email, send_automatic_whatsapp, require_document_photo. - update (signer_token, data): atualiza (só antes de assinar) ou reenvia lembrete. Mesmos campos de add. - remove (signer_token): remove (não pode remover quem já assinou nem o único signatário). - sign (data): assina em lote via API (assíncrono). Campos: signer_tokens[]*; opc selfie_photo, document_photo_url. (user_token é injetado automaticamente.) [Flattened action: add]

zapsign_signers_write_remove

zapsign_signers_write_sign

zapsign_signers_write_update

zapsign_templates_get

Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: get]

zapsign_templates_list

Templates (modelos DOCX) no ZapSign (leitura). Ações: list (page — 20/página); get (template_token — inclui inputs[] das variáveis {{VAR}}). [Flattened action: list]

zapsign_templates_write_create

Gerenciar templates no ZapSign. Ações: - create (data): cria template DOCX. Campos: name*, docx_url | base64_docx*; opc first_signer{}, lang, observers[], folder_path/folder_token, redirect_link. - update (template_token, data): metadados (o DOCX em si é imutável). Campos: name, lang, observers[], first_signer, folder_path/token, redirect_link. - delete (template_token): irreversível. [Flattened action: create]

zapsign_templates_write_delete

zapsign_templates_write_update

zapsign_webhooks_write_create

Gerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove webhook pelo id retornado na criação. [Flattened action: create] Bulk support: accepts ids for batched execution.

zapsign_webhooks_write_delete

Gerenciar webhooks no ZapSign (não há endpoint de listagem na API). Ações: - create (data): cria webhook (1 por conta cobre todos os docs). Campos: url*; opc type ("" = todos | doc_signed | doc_created | doc_deleted | ...), doc_token, headers. Retorna {id}. - delete (id): remove webhook pelo id retornado na criação. [Flattened action: delete] Bulk support: accepts ids for batched execution.

authenticate

authenticate

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

connect

connect

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

marketplace

marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

report

report_bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

show

show_version

Show the current MCP platform and adapter versions.

toolkit

toolkit_info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Endpoints

URL	Transport	State	Latency	Checked
https://api.mcp.ai/p_zapsign	streamable-http	answering	423 ms	1 min ago

Alternatives to ZapSign

same job, measured the same way

FreeSign — Free e-signature

by free-sign

Free e-signature for humans and AI agents — zero-document PDF signing from hashes only.

5 tools answering

The Office Worker

by cafra-house

Local-first document MCP for AI agents: create, read, secure and sign PDF/Word/Excel/PPTX.

3 632 installs/wk local only

Signforge

by kumarprobeops

Send documents for e-signature from AI agents. Upload, sign, and download PDFs.

39 installs/wk local only

Pdfgate

by pdfgate

MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.

218 installs/wk answering

Zsign

by zsign

E-signature API for AI agents: send contracts, sign PDF documents, track and download signed files.

answering

blue·auth Document Signing

by ricdanyalgil

Send AI-created PDFs for signature, track signers, and return verifiable document evidence.

answering

Signvoy

by signvoy

Send documents for e-signature, track signing status, and download signed PDFs. No API key required.

answering

Addsign MCP

by rmindgh

Send documents for e-signature, track status, remind signers, and download signed PDFs via AddSign

32 installs/wk local only

ZapSign — questions

Answers built from our own checks of this server.

What can ZapSign do?

It exposes 35 tools, read directly from the server on our last check. Among them: authenticate, connect, marketplace, report_bug, show_version, toolkit_info and 29 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is ZapSign working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1090 ms. The bar chart above shows every period we have measured.

How do I connect ZapSign?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does ZapSign need an API key?

No. ZapSign completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 35 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ZapSign?

It answers our handshake in 1090 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is ZapSign open source?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.