Claude cannot produce a PDF invoice on its own; it writes text in chat. To get an actual invoice.pdf, give Claude an MCP server that has an invoice generator, then ask for the invoice in plain language and download the PDF it returns.
https://mcp.zovo.one/mcp/invoice/t/<token>..mcp.json instead:{
"mcpServers": {
"invoice": {
"url": "https://mcp.zovo.one/mcp/invoice/t/<token>"
}
}
}
/mcp/connect.The invoice MCP server is hosted at mcp.zovo.one with a free anonymous tier; a Pro key ($19 single, $39 bundle) replaces the token in the same URL for higher limits. The same connector URL pattern works in Cursor and VS Code.
Before blaming the assistant, confirm the server answers a real call. Discovery alone is not proof — initialize and tools/list answer 200 even with a bad token, but this is the exact request shape to start from:
curl -s https://mcp.zovo.one/mcp/invoice/t/<token> \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
If this returns a tool list, the token and URL are good and any remaining problem is in the client’s connector settings.
A hosted invoice server typically carries tools for creating an invoice from line items, listing previously issued invoices, and numbering. Create one tool call per document; do not ask for several invoices in a single request, because one failure then blocks all of them. Keep line item descriptions short and pass tax as a rate plus a label, not a precomputed amount.
The server that does this: Invoice — 11 tools, free locally (MIT), $19 one-time for the hosted endpoint. Read the server page · Buy the licence.