E-signature API and MCP server

Send a document in two calls

Type a glyph into the document wherever a field goes: \s1\ for the first signer's signature, \d1\ for the date they sign, \s2\ for the second signer. Upload it once as a template; a Word file is converted to PDF and the glyphs are read from it. Every call goes to api.signwithsigil.com.

curl https://api.signwithsigil.com/v1/templates \
  -H "Authorization: Bearer $SIGIL_API_KEY" \
  -F file=@agreement.docx -F name="Consulting agreement"

Then create a pact from it with the signers in signing order, and send it in the same call:

curl -X POST https://api.signwithsigil.com/v1/pacts \
  -H "Authorization: Bearer $SIGIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "template_uid": "7DXW69YJ", "send": true,
        "recipients": [ { "name": "Avery Lane", "email": "avery@example.com" },
                        { "name": "Sam Ortiz", "email": "sam@example.com" } ] }'

Each signer is emailed a private link when it is their turn. When the last one signs, GET /v1/pacts/{uid}/signed.pdf and sigil.pdf return the stamped document and its certificate of completion, and every recipient gets both by email. A one-off document goes straight into POST /v1/pacts as a file part instead.