{
  "mcpServers": {
    "siglio": {
      "command": "npx",
      "args": ["-y", "siglio-mcp"],
      "env": { "SIGLIO_API_KEY": "sig_sandbox_your_key_here" }
    }
  }
}

Other MCP clients take the same command and environment.

What it can do

Tool	What it does
`send_for_signature`	Sends a PDF to one or two people, by email, text, or both
`check_envelope`	Whether it has been delivered, opened, signed or cancelled
`download_signed_document`	Saves the completed PDF once every signature is in
`void_envelope`	Cancels an unsigned envelope; the link stops working

Then you can just ask: "Send the NDA on my desktop to Dana at 813 555 0142 by text."

The one thing to know about your PDF

Siglio does not take coordinates for signature fields. Placement comes from literal text tags inside the document itself:

^S1   signer one signs here        ^S2   signer two signs here
^I1   signer one initials here     ^I2   ...
^D1   a date that fills itself     ^D2   ...

Set that tag text to white font before you save the PDF. The tags are instructions, not content, and black ones stay visible on the signed document.

If the tags are missing the send is rejected and nothing goes out, so you cannot accidentally mail someone a document they have no way to sign.

Two safety decisions worth knowing

Live keys are refused by default. A key starting with sig_live_ will not run unless you also set SIGLIO_ALLOW_LIVE=true. Until you do that, the worst a confused assistant can do is send a free sandbox envelope. Sandbox envelopes deliver for real and produce real signatures; they just cost nothing.

Sending is idempotent by content. If an assistant retries the same document to the same people, it gets the first envelope back instead of putting a second copy of a contract in someone's inbox.

Cancelling additionally requires an explicit confirmation, so it cannot happen as a side effect of a vague instruction.