Command line

sigil is a small command-line client for the API. It is the tool for scripts, for CI, and for coding agents such as Claude Code, Codex and Cursor, which work with files on disk: the MCP server can only send templates that are already uploaded, while the CLI uploads the file in front of it. It is published on npm as @signwithsigil/cli, MIT-licensed, with the source on GitHub.

Install

It needs Node.js 20 or later and has no other dependencies:

npm install -g @signwithsigil/cli
sigil --version

npx @signwithsigil/cli --version

Upgrade with the same npm install -g command; the CLI only calls the public API, so an older version keeps working.

Sign in

sigil login

Your browser opens a Sigil page; log in and allow the connection. The CLI keeps its tokens in ~/.config/sigil/credentials.json (%APPDATA%\sigil on Windows), readable only by you, and refreshes them on its own. Using the API needs the Pro or Business plan.

Where a browser is not available, such as CI, set an API key instead; it takes precedence over a sign-in:

export SIGIL_API_KEY="sgk_…"

sigil logout forgets the sign-in and revokes it on the server; sigil whoami shows the account, plan and documents left.

Send a document

The shortcut takes a file (PDF or Word, with glyphs typed where the fields go) or a saved template's id, and one --to per signer, in signing order:

sigil send agreement.pdf \
  --to "Avery Lane <avery@example.com>" \
  --to "Sam Ortiz <sam@example.com>" \
  --cc records@example.com \
  --title "Consulting agreement with Acme" \
  --message "Please sign by Friday." \
  --lapse-days 14

Pact 7DXW69YJ sent: 2 signers, 1 document used.
Avery Lane <avery@example.com> has been emailed their signing link.

A file is uploaded as a one-off document; a template id (sigil send 7DXW69YJ …) reuses the saved one. Sending uses one document per 3 signers; the command refuses, before anything is sent, when the account has too few left.

Commands

Every command takes --json to print the API's response unchanged, for scripts:

sigil pacts list --status sent --json | jq '.data[] | {uid, title, status}'

Exit codes: 0 success, 1 the API refused (the message is on stderr, in the API's words), 2 usage.

In a coding agent

Claude Code, Codex and Cursor can run sigil like any other command once it is installed and signed in. Tell the agent to use it, or install the Sigil plugin, whose skill explains the flow: check sigil whoami for documents left, prefer a draft and show it before sigil pacts send, and never guess an email address.

As a local MCP server

Some clients can only start local (stdio) MCP servers. sigil mcp is a bridge: it reads MCP messages on standard input, forwards them to the hosted server with your sign-in, and writes the answers back. Sign in first with sigil login, then register the command:

{
  "mcpServers": {
    "sigil": { "command": "sigil", "args": ["mcp"] }
  }
}

{
  "command": "npx",
  "args": ["-y", "@signwithsigil/cli", "mcp"]
}

Clients that connect to remote servers themselves (Claude, Claude Code, Codex, ChatGPT, Cursor, VS Code) do not need the bridge: give them the server URL as on Connect a client.

Environment

Source and issues

The CLI is open source under the MIT license: github.com/signwithsigil/cli. Report a problem as an issue there, or through the contact page.