Kamy

What is Kamy?

Kamy is a developer-first MCP for the full document chain: generate, sign, edit, verify, audit. It replaces a typical stack of DocuSign, a PDF generation API, and a homegrown audit logger with one vendor and one API. It renders PDFs from templates, applies PAdES B-LT cryptographic signatures, edits existing PDFs, and produces a tamper-evident audit trail anyone can verify without a Kamy account.

How to use Kamy?

Install Kamy as an MCP server by adding the URL https://mcp.kamy.dev/mcp and your API key in Claude Code or Cursor. Use exposed tools such as render_pdf, sign_pdf, edit_pdf, verify_pdf, list_templates, install_sdk, and ask_kamy. The canonical flow is generate → sign → prove.

Key features of Kamy

• Generate PDFs from templates or raw HTML/CSS
• Sign with PAdES B-LT cryptographic seals (own CA, RFC 3161 timestamps, embedded CRL)
• Edit, fill AcroForm widgets, stamp text, and redact PII on existing PDFs
• Independent verification of signed documents forever, without a Kamy account
• Includes system templates: invoice, contract, certificate, shipping-label, and more
• TypeScript and Python SDKs available

Use cases of Kamy

• AI agents that produce documents with tamper-evident, verifiable receipts
• Compliance-grade SaaS needing cryptographically signed PDFs (fintech, healthtech, regtech)
• Embedded document workflows where customers need contracts, invoices, or receipts inside a product

FAQ from Kamy

What does Kamy replace?

Kamy replaces a typical stitched stack of DocuSign + a PDF generation API + a homegrown audit logger with one vendor, one API, and one audit boundary.

How does independent verification work?

Every signed Kamy document is independently verifiable forever by anyone without trusting Kamy. The PAdES signature chains to a CA, the timestamp chains to FreeTSA, and the audit row chains to a public hash. Drag any signed PDF into https://kamy.dev/verify to check.

What is included in the free tier?

The free tier ($0) includes 100 renders/month, 10 e-signatures/month, PAdES B-LT signing, PDF/A output, a public verify page, and MCP server access. No credit card required.

What are the runtime requirements?

You need an API key from kamy.dev/dashboard/api-keys. The MCP server uses HTTP transport (Claude Code) or streamable-http (Cursor). Authentication is via the KAMY_API_KEY environment variable.

What templates are available out of the box?

System templates include invoice, receipt, quote, contract, agreement, certificate, shipping-label, and report, plus country-compliant tax variants (UAE FTA, KSA ZATCA, EU VAT, US 1099-NEC).