markdown2pdf
Convert markdown to PDF, and pay with Lightning
LABSCO 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
USE CASES
01
Sending a written answer out as a document
The markdown you already have becomes a titled, dated PDF in one call, with the conversion paid for over Lightning as part of the same request.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"markdown2pdf-mcp": {
"command": "npx",
"args": [
"@serendipityai/markdown2pdf-mcp"
]
}
}
}npx
TERMINAL
npx @serendipityai/markdown2pdf-mcp
