Test it live

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

Prerequisites

  • ZapSign account with api_token.
  • Codex CLI: npm install -g @openai/codex.
  • Node.js 18+.

Step by step

Connect via URL Recommended

~/.codex/config.tomlTOML
[mcp_servers.zapsign]
type = "url"
url = "https://mcp.zapsign.com.br/mcp"

Codex opens an OAuth/authorization flow on first connect. Paste your api_token.

Verify the connection

terminalbash
codex
# inside the session:
/mcp

Test with a real document

Sample promptchat
Create a ZapSign document named "Codex 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 config.toml
~/.codex/config.tomlTOML
[mcp_servers.zapsign]
command = "npx"
args = ["-y", "mcp-server-zapsign"]

[mcp_servers.zapsign.env]
ZAPSIGN_API_KEY = "your_api_token"
ZAPSIGN_BASE_URL = "https://sandbox.zapsign.com.br/api/v1"

Automation ideas

  • Onboarding script: "for each CSV row, create a contract from template X and email column 2."
  • Audit: "list all pending documents this month and summarize in Markdown."
  • Contract CI: generate staging documents after each release.

Common issues

SymptomLikely cause and fix
Server missing in /mcpInvalid TOML or wrong section name — must be [mcp_servers.zapsign].
401 UnauthorizedWrong token. Regenerate and reconnect.
Startup timeout (stdio)First npx download is slow. Run it once manually.

Next steps