Test it live

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

Prerequisites

  • ZapSign account with api_token.
  • Cursor installed.

Step by step

Add via URL Recommended

Open Cursor Settings → MCP → Add new MCP server and paste:

ZapSign MCP server URLURL
https://mcp.zapsign.com.br/mcp

Authorize with your api_token from ZapSign Settings → Integrations → API.

Test in the agent loop

Sample promptchat
Using ZapSign, create a document named "Cursor test"
from https://zapsign.s3.amazonaws.com/exemplo.pdf
with signer Your Name <you@company.com>
and return the signing link.

The agent can now create real documents while you iterate on integration code.

Alternative: mcp.json (global or project)

Global: ~/.cursor/mcp.json. Per project: .cursor/mcp.json.

mcp.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
Tools not listedReload MCP servers in Cursor Settings, or restart Cursor.
401 UnauthorizedWrong token. Regenerate and update the connector or mcp.json.
npx timeoutRun npx -y mcp-server-zapsign once manually to warm the cache.

Next steps