Carbone

@Carbone check server status and list all available templates with their IDs and upload dates

The Carbone server is operational (status: healthy, uptime: 99.8%). Here are your available templates: 1. invoice_template_2024.docx (ID: a3f7b2c1...) - uploaded Jan 15, 2024 2. contract_standard.odt (ID: d8e9f1a2...) - uploaded Feb 3, 2024 3. monthly_report.xlsx (ID: b4c5d6e7...) - uploaded Mar 10, 2024 All templates are ready for report generation. This example assumes a typical response structure; actual template metadata depends on your Carbone account's stored files.

This demonstrates the server health check and template listing capabilities. Requires valid API_KEY authentication. Note that Carbone's template storage is account-specific—your actual template list will differ. Use this workflow before bulk report generation to verify service availability.

@Carbone generate a PDF invoice from template ID a3f7b2c1 using this JSON data: customer name 'Acme Corp', invoice number 'INV-2024-089', line items with quantities and prices

Report generated successfully. The invoice PDF has been rendered using template a3f7b2c1 with your provided data: - Customer: Acme Corp - Invoice #: INV-2024-089 - 3 line items processed - Total calculated: $2,847.50 Download link: [carbone-render-xyz123.pdf] (expires in 24 hours). This example shows typical generation output; actual formatting depends on your template's design and the JSON structure you provide.

This showcases Carbone's core document generation capability. The MCP transforms JSON data into formatted documents (PDF, DOCX, XLSX, etc.) based on your pre-uploaded templates. Side-effect: creates a temporary file on Carbone's servers. Ensure your template's placeholders match your JSON keys exactly, or rendering will fail silently for mismatched fields.

@Carbone upload this contract template file, generate its template ID, then create a test render with sample client data to verify all merge fields populate correctly

Template uploaded successfully. Generated template ID: f9a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5. Running test render with sample data: Test report generated. Verification results: ✓ Client name field: populated ✓ Contract dates: populated ✓ Payment terms table: 4 rows rendered ⚠ Signature block: placeholder text still visible (check JSON key 'signatory_name') This example illustrates the upload-test workflow; actual field validation depends on your template's structure and the sample JSON you provide.

This combines three tools (upload, ID generation, test render) into a validation workflow. Useful for catching template errors before production use. Requires write permissions via API_KEY. The test render creates a temporary file—consider deleting it after verification to avoid clutter. Carbone doesn't auto-validate merge fields, so this AI-assisted check helps catch mismatches early.

When Carbone beats manual invoice formatting for recurring billing

A 6-person consulting shop sends 40-60 invoices monthly, each pulling line items from Stripe and contract details from Notion. Carbone wins here because you upload one .docx template with merge tags, then the AI generates invoices by calling the Generate Carbone Report tool with JSON from your data sources. No more copy-pasting into Google Docs or fighting with PDF libraries. The threshold: if your invoice format changes more than once a quarter, template management gets tedious—you're uploading, generating IDs, and deleting old versions through seven separate tools. But for stable formats and moderate volume, Carbone turns a 90-minute monthly chore into a 10-minute AI prompt.

Why Carbone fits HR teams with 5-20 templates

A 12-person startup onboards 2-3 people monthly, each needing an offer letter, equity agreement, benefits summary, and handbook addendum—all pulling from BambooHR and the employee's Slack profile. Carbone handles this because HR uploads the four templates once, then the AI calls Generate Carbone Report for each document in a single thread, merging live data into PDFs. The trade-off: if you're onboarding one person every six months, the setup overhead (API key, template uploads, version management) outweighs the payoff. But at 20+ documents a year with consistent formats, Carbone eliminates the manual merge-and-export loop that eats an hour per hire.

When Carbone saves time on slide decks with live metrics

A 4-person executive team updates a 30-slide board deck quarterly, pulling revenue charts from Stripe, headcount from Rippling, and roadmap status from Linear. Carbone works if the deck template is stable—upload the .pptx once, then the AI regenerates it with fresh JSON each quarter via Generate Carbone Report. The catch: Carbone's seven tools don't include direct integrations, so you're still wrangling data from other MCPs or APIs into the right JSON shape. If your deck structure changes every quarter or you need real-time collaboration, Google Slides with manual updates is faster. But for a locked template and predictable data sources, Carbone turns a two-day refresh into a 20-minute AI session.