MCP.so
Sign In

Kamy MCP Server

@Kamy-Development

Basic information

Category

Developer Tools

Transports

stdio

Author

Kamy-Development

Submitted by

rakanalalami

About Kamy MCP Server

The document layer for AI-native software. From your agent runtime, generate PDFs from templates, sign them with PAdES B-LT cryptographic signatures (own CA, RFC 3161 timestamps, embedded CRL), edit / fill / redact existing PDFs, and produce a tamper-evident audit trail anyone ca

Kamy MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "kamy": {
      "url": "https://mcp.kamy.dev/mcp",
      "transport": "streamable-http",
      "env": {
        "KAMY_API_KEY": "<YOUR_KAMY_API_KEY>"
      }
    }
  }
}

Kamy MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

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

Frequently asked questions

1

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.

2

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.

3

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.

4

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.

5

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).

Comments

More Developer Tools MCP servers