The Kamy MCP server,
connected in one click.

“Use “list_templates”: List Kamy's public system PDF templates. No authentication required.”

“Use “get_template_schema”: Fetch the JSON Schema (exact data shape) and a copy-pasteable sample payload for a Kamy system template by slug. Call this before render_pdf.”

“Use “create_template”: Create a new custom PDF template owned by this account: a name, a unique slug, a Handlebars/HTML body, and optional CSS and JSON Schema. The.”

“Use “update_template”: Edit an existing custom template's DRAFT — name, html, css, schema, tags, visibility — addressed by UUID or slug. Only the fields you pass a.”

list_templates — List Kamy's public system PDF templates. No authentication required.

get_template_schema — Fetch the JSON Schema (exact data shape) and a copy-pasteable sample payload for a Kamy system template by slug. Call this before render_pdf

create_template — Create a new custom PDF template owned by this account: a name, a unique slug, a Handlebars/HTML body, and optional CSS and JSON Schema. The

update_template — Edit an existing custom template's DRAFT — name, html, css, schema, tags, visibility — addressed by UUID or slug. Only the fields you pass a

publish_template — Make a template version live for rendering. Called with no `version`, it snapshots the current draft into a new version and points published

rollback_template — Revert a template after a bad release: repoints published_version at the version you name, so every subsequent render immediately serves tha

list_template_versions — List a template's immutable version snapshots, newest first, as { id, version, createdAt }. This is where the version number that publish_te

get_template_version — Fetch one template version snapshot in full — html, css, schema, createdBy, createdAt — exactly as it was frozen when that version was cut.