ZapSign MCP server

Connect ZapSign and your agent gets 35 tools, among them authenticate, connect, marketplace. It answers at https://api.mcp.ai/p_zapsign over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status

Answering

Tools

Reliability

6 of 6 checks

Response time

472 ms

Transport

streamable HTTP

Last checked

22 October 2026

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

Description as the publisher wrote it.

The 35 tools ZapSign offers

Tool	What it does
`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-on Inputs: token
`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`	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 Inputs: action, query, mcp_id, limit, tier_slug, immediate
`report_bug`	Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. Inputs: message, context, conversation
`show_version`	Show the current MCP platform and adapter versions.
`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.
`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] Inputs: page, account
`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] Inputs: page, account
`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 Inputs: email, data, account
`zapsign_account_write_delete_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 Inputs: email, data, account
`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. Inputs: check_id, account, check_ids
`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. [Flattene Inputs: data, account
`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 — detalh Inputs: doc_token, status, folder_path, deleted, signer_email, created_from
`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 — detalh Inputs: doc_token, status, folder_path, deleted, signer_email, created_from
`zapsign_documents_signer_log`	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 — detalh Inputs: doc_token, status, folder_path, deleted, signer_email, created_from
`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 \| base6 Inputs: doc_token, data, account
`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 \| base6 Inputs: doc_token, data, account
`zapsign_documents_write_create_from_template`	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 \| base6 Inputs: doc_token, data, account
`zapsign_documents_write_delete`	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 \| base6 Inputs: doc_token, data, account
`zapsign_documents_write_place_signatures`	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 \| base6 Inputs: doc_token, data, account
`zapsign_documents_write_refuse`	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 \| base6 Inputs: doc_token, data, account
`zapsign_documents_write_update`	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 \| base6 Inputs: doc_token, data, account
`zapsign_list_accounts`	Lista contas ZapSign vinculadas a este install — id e apelido. Inputs: account
`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] Inputs: signer_token, account
`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, qualificatio Inputs: doc_token, signer_token, data, account
`zapsign_signers_write_remove`	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, qualificatio Inputs: doc_token, signer_token, data, account
`zapsign_signers_write_sign`	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, qualificatio Inputs: doc_token, signer_token, data, account
`zapsign_signers_write_update`	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, qualificatio Inputs: doc_token, signer_token, data, account
`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] Inputs: template_token, page, account
`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] Inputs: template_token, page, account
`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 ( Inputs: template_token, data, account
`zapsign_templates_write_delete`	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 ( Inputs: template_token, data, account
`zapsign_templates_write_update`	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 ( Inputs: template_token, data, account
`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, heade Inputs: id, data, account, ids
`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, heade Inputs: id, data, account, ids

Add ZapSign to your AI client

Every block below points at https://api.mcp.ai/p_zapsign. Pick your client and copy.

Claude Code: one command in your terminal

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

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "zapsign": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.mcp.ai/p_zapsign"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

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

VS Code and GitHub Copilot: .vscode/mcp.json

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

Zed: Zed settings.json

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

Windsurf: ~/.codeium/mcp_config.json

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

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

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

Continue: .continue/mcpServers/neuronto.yaml

name: ZapSign
version: 0.0.1
schema: v1
mcpServers:
  - name: ZapSign
    type: streamable-http
    url: https://api.mcp.ai/p_zapsign

Gemini CLI: ~/.gemini/settings.json

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

Codex CLI: MCP server config

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

Warp: MCP servers, + Add, paste JSON

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

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fapi.mcp.ai%2Fp_zapsign&type=streamable_http&id=zapsign&name=ZapSign

Is ZapSign up right now?

It answered our last check on 22 October 2026 in 472 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to ZapSign

Zsign0 tools APISign0 tools Signvoy0 tools FreeSign — Free e-signature5 tools SignSimple4 tools Okdoc0 tools

Questions about ZapSign

How many tools does ZapSign have?

35, as returned by the server's own tools/list on 17 September 2026: authenticate, connect, marketplace, report_bug, show_version, toolkit_info, zapsign_account_plan, zapsign_account_users, and 27 more.

Is ZapSign down?

It answered our last check on 22 October 2026 in 472 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add ZapSign to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.mcp.ai/p_zapsign. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does ZapSign need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.mcp-dir. Endpoint host: api.mcp.ai. ARD identifier: urn:air:io.github.mcp-dir:mcp:zapsign-mcp. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.