Sign Cli
Enable your agent to apply offline PAdES e-signatures and append hash-chained audit records without a SaaS e-sign vendor.
Overview
sign-cli is a MCP server for the Ship phase that provides offline PAdES e-signing and hash-chained audit tools for agent-driven documents.
What is this MCP server?
- Agent-first MCP server for e-signature workflows via @drbaher/sign-cli
- Offline PAdES signing without requiring a cloud e-sign API for every document
- Hash-chained audit log for traceable signature events
- stdio npm transport for Claude Code and Cursor
- Version 0.7.1 package suitable for repeatable agent-driven document closure
- MCP server version 0.7.1
- npm package @drbaher/sign-cli with stdio transport
- Offline PAdES signing with hash-chained audit as stated capabilities
What problem does it solve?
Relying on ad-hoc PDF exports or opaque cloud e-sign APIs makes it hard for agents to sign contracts with verifiable audit trails under your control.
Who is it for?
Indie founders and technical solo builders who want local, agent-triggered signing with compliance-oriented audit logging.
Skip if: Non-technical users who need polished multi-signer email workflows and hosted legal templates only.
What do I get? / Deliverables
Your agent can sign documents with PAdES offline and maintain a hash-chained audit chain you can verify later.
- PAdES-signed PDF or signature artifacts produced offline
- Hash-chained audit entries for signature-related events
- Agent-repeatable signing workflow without a mandatory e-sign SaaS API
Recommended MCP Servers
Journey fit
How it compares
Cryptographic signing MCP, not a general document editor or consumer e-sign marketplace.
Common Questions / FAQ
Who is sign-cli for?
Builder-operators and agent users who sign PDFs programmatically and care about PAdES, offline operation, and auditable hash chains.
When should I use sign-cli?
Use it when shipping contracts or compliance documents where you want the coding agent to sign or orchestrate signing with local keys and recorded audit events.
How do I add sign-cli to my agent?
Install @drbaher/sign-cli from npm, add it as a stdio MCP server in your agent config, and configure certificates and keys per the sign-cli repository documentation before enabling sign tools.