To produce a customer quote PDF, connect an MCP quotes server and ask for the quote in chat: line items, quantities, prices, validity period, and the assistant returns a formatted quote document as a download link.
https://mcp.zovo.one/mcp/quotes/t/<token> in Cursor’s .mcp.json:{
"mcpServers": {
"quotes": {
"url": "https://mcp.zovo.one/mcp/quotes/t/<token>"
}
}
}
The quotes MCP server is hosted free at mcp.zovo.one (anonymous tier; Pro $19 single, $39 bundle). Companion servers: invoice, credit-note, price-tracker, billing-docs.
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/quotes/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 quotes server stores quotes with an identifier, line items and a validity period. When a quote is accepted, reference the same quote id when generating the invoice so the two documents stay traceable to each other; that pairing is also what a credit-note tool expects if part of the deal is reversed.
When a client negotiates, issue a revised quote with a new version suffix (Q-1077-r2) rather than overwriting the original, and reference the original id in the request. Keeping both versions lets you show what changed without reconstructing it from chat history.
The server that does this: Quotes — 10 tools, free locally (MIT), $19 one-time for the hosted endpoint. Read the server page · Buy the licence.