Summary
A written answer leaves the chat as a document, and settles itself on the way out.
There is one call, carrying the title, the date and the document itself, so the decision to produce a PDF costs a sentence rather than a toolchain. Payment sits inside that call over Lightning instead of behind an account you set up first, which is unusual enough to plan for: whatever pays needs to be ready before the tool is useful.
What it is
A one-tool markdown-to-PDF converter with Lightning payment in the call path
What you get
- A PDF produced from markdown passed in as text_body, with title and date supplied as arguments (markdown2pdf).
- Payment over Lightning as part of the same conversion call.
Requirements
A way to pay over Lightning, since payment is part of the conversion. The document travels in the call itself: title, date and text_body.
Setup effort
One command — npx @serendipityai/markdown2pdf-mcp