Test it live

Run this flow in ZapSign Builders — the interactive REST API playground. Open in Builders →

Prerequisites

  • ZapSign account with api_token.
  • Gemini CLI: npm install -g @google/gemini-cli.
  • Node.js 18+.

Step by step

Connect via URL Recommended

~/.gemini/settings.jsonJSON
{
  "mcpServers": {
    "zapsign": {
      "type": "url",
      "url": "https://mcp.zapsign.com.br/mcp"
    }
  }
}

Verify with /mcp

terminalbash
gemini
# inside the session:
/mcp

The zapsign server should show as CONNECTED.

Test with a real document

Sample promptchat
Create a ZapSign document named "Gemini test" from
https://zapsign.s3.amazonaws.com/exemplo.pdf, add
Your Name <you@company.com> as signer and return
the signing link.
Alternative: stdio in settings.json
~/.gemini/settings.jsonJSON
{
  "mcpServers": {
    "zapsign": {
      "command": "npx",
      "args": ["-y", "mcp-server-zapsign"],
      "env": {
        "ZAPSIGN_API_KEY": "your_api_token",
        "ZAPSIGN_BASE_URL": "https://sandbox.zapsign.com.br/api/v1"
      }
    }
  }
}

Common issues

SymptomLikely cause and fix
Server DISCONNECTED in /mcpWrong URL or invalid token. Confirm https://mcp.zapsign.com.br/mcp and reconnect.
401 UnauthorizedWrong token. Regenerate and reconnect.
Tool not calledBe explicit ("using ZapSign tools") or check for conflicting MCP server names.

Next steps