E-signature is only worth anything because of the audit record, and plenty of integrations expose the signed file while leaving the certificate somewhere in a web UI. Here it is a separate call, with an archive option that bundles both. The other thing this surface does well is state: every tool names the envelope state it requires, so an agent working a queue knows that voiding needs a sent envelope and deleting does not work on one — which is the difference between a clean refusal and a batch that half-completes. Worth remembering what create_and_send actually does: it sends. A signature request goes to a real person the moment that call returns.
An e-signature client covering the envelope lifecycle: create and send, track status, download the signed output and its audit trail, plus templates, webhooks and embeddable signing.
- create_and_send does the whole opening move in one call — envelope, PDF, signer, sent — while send_envelope covers the case where a draft already exists.
- check_status returns recipient signing state, and list_envelopes filters by status so a queue can be worked.
- Three download paths with different contents: the signed PDF, the audit certificate with its full trail, and a ZIP archive containing both plus related documents.
- The state machine is enforced and each tool says so: download_signed needs a completed envelope, void_envelope needs a sent one, and delete_envelope only accepts drafts and voided envelopes.
- get_embed_url returns a signing URL for an iframe, so signing can happen inside your own product.
- Webhooks are managed here rather than in a console — create, list and delete, with deletion stopping events immediately.
- Templates hold pre-placed fields, and create_from_template can pre-fill values and send in the same call.
SIGNFORGE_API_KEY.
One command plus a key — SIGNFORGE_API_KEY="your-api-key-here" npx -y @signforge/mcp-server, then supply credentials