Kamy
Render PDFs, collect e-signatures, apply PAdES seals, and verify documents from your agent via Kamy’s document API MCP.
Overview
dev.kamy/kamy is an MCP server for the Build phase that integrates PDF rendering, e-sign, PAdES sealing, and document verification for AI-native apps.
What is this MCP server?
- Remote MCP at mcp.kamy.dev/mcp (streamable HTTP), server version 1.2.0
- PDF rendering, e-sign, PAdES-seal, and verification in one document API surface
- GitHub plugin source at Kamy-Development/kamy-plugin
- Positioned for AI-native software that must produce legally meaningful PDFs
- MCP server version 1.2.0
- Remote endpoint mcp.kamy.dev/mcp
- Capabilities advertised: render PDFs, e-sign, PAdES-seal, verify
What problem does it solve?
Shipping signed PDFs from an agent workflow means fragile one-off integrations for render, sign, seal, and verify steps.
Who is it for?
Indie SaaS founders automating contracts, invoices, or compliance PDFs with PAdES-aware sealing from Claude Code or Cursor.
Skip if: Static sites with no generated documents or teams that only need unsigned markdown exports.
What do I get? / Deliverables
Your agent can call one MCP-backed document pipeline to produce and cryptographically validate PDFs inside the product you are building.
- Agent-generated PDFs with e-sign or PAdES seal applied
- Verification results for signed document artifacts
- Integrated document path in your SaaS without custom HSM glue in v1
Recommended MCP Servers
Journey fit
Document generation and signing are integration work while you build contracts, onboarding packs, or compliance-heavy SaaS features. integrations covers third-party document pipelines that agents call instead of you maintaining wkhtmltopdf and PKCS#11 glue locally.
How it compares
Document and e-sign API MCP, not a local PDF markdown skill.
Common Questions / FAQ
Who is dev.kamy/kamy for?
Solo builders creating AI-native apps that must generate PDFs, capture e-signatures, and verify PAdES-sealed documents through an agent.
When should I use dev.kamy/kamy?
Use it during build when you wire onboarding, billing, or contract flows that need rendered PDFs and verifiable signatures from the agent stack.
How do I add dev.kamy/kamy to my agent?
Add remote MCP https://mcp.kamy.dev/mcp to your client config and authenticate per Kamy’s plugin docs on GitHub.