Docs
Propale Docs — API & MCP
REST first, then MCP. Structured JSON in → commercial proposal PDF out. API keys are product-scoped — not personal OAuth.
Full OpenAPI reference lands with the API surface. This hub is live so landing CTAs resolve.
Connect an MCP client
MCP is available at /mcp over authenticated HTTP. Use the same revocable account API key as REST in an Authorization: Bearer header.
create_proposal, create_quote, and create_invoice are live and return authenticated document metadata plus PDF URLs. Quotes and invoices calculate VAT totals server-side.
POST /mcp
Authorization: Bearer <account-api-key>
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"create_proposal","arguments":{...proposal}}}GET /mcp also exposes the small SSE endpoint advertisement for legacy MCP HTTP/SSE clients.