Documentero

@documentero list all available templates in my account and show me what formats each one supports

Found 8 templates in your Documentero account: • Invoice Template (ID: tpl_inv_2024) — supports PDF, DOCX • Employee Onboarding Packet (ID: tpl_onboard_v3) — supports PDF only • Quarterly Report (ID: tpl_qtr_report) — supports PDF, DOCX, XLSX • NDA Standard (ID: tpl_nda_std) — supports PDF, DOCX • Project Proposal (ID: tpl_proposal_2023) — supports PDF, DOCX Each template can be generated by referencing its ID. Use the metadata endpoint to see required fields before generating.

This read-only call shows what templates your API key can access. Useful for discovery before generating documents. No side effects, but the list reflects only templates visible to your account's current plan tier.

@documentero generate a PDF invoice from template tpl_inv_2024 with client name 'Acme Corp', invoice number 'INV-1234', amount '$5,200', and due date '2025-02-15'

Document generated successfully. Your invoice PDF is ready: **Download URL:** https://documentero-cdn.com/signed/abc123xyz.pdf?expires=1738195200 **Expires:** 2025-01-30 at 12:00 UTC (24 hours from now) The file contains a formatted invoice with the provided details. This generation consumed 1 credit from your plan balance (47 credits remaining this month).

This write action creates a real document and consumes plan credits. The signed URL expires in 24 hours by default. If you need the file persisted elsewhere, download it immediately or request base64 encoding to store in your own system. Rate limits apply per your Documentero plan tier.

@documentero get the schema for template tpl_onboard_v3 so I can see what fields are required, then draft sample data for a new hire named Jordan Lee starting March 1st

**Template Schema (tpl_onboard_v3):** ```json { "employee_name": "string (required)", "start_date": "string (required, format: YYYY-MM-DD)", "department": "string (required)", "manager_name": "string (required)", "equipment_list": "array of strings (optional)" } ``` **Drafted Sample Data:** ```json { "employee_name": "Jordan Lee", "start_date": "2025-03-01", "department": "Engineering", "manager_name": "[Your Manager Name]", "equipment_list": ["Laptop", "Monitor", "Keyboard", "Mouse"] } ``` You can now generate the onboarding packet by passing this data to the template.

This pairs schema introspection with AI reasoning to prepare valid input data. The schema call is read-only and free; generating the document afterward will consume credits. Useful for validating data structure before committing to generation, especially with complex nested fields.

When Documentero beats manual proposal assembly for 3-8 person teams

A 6-person creative agency closes 4-5 proposals a month, each pulling scope details from Linear, budget tables from internal spreadsheets, and client briefs from Slack threads. Documentero wins here because the 4-tool scope lets you template the proposal structure once in DOCX or PDF, then pipe live data from other MCPs (Linear for deliverables, Google Sheets for pricing) into each generation call. The JSON schema tool means your prompt can validate data shape before sending, catching missing fields before the doc renders. The trade-off: if your proposals need heavy conditional logic or multi-step approvals, you'll hit the template editor's limits fast. This works when your proposal structure is stable and the variance lives in the data, not the layout. If you're closing 2+ deals a week with repeatable scopes, the time saved on manual assembly pays for itself in month one.

Why Documentero falls short for infrequent high-stakes documents

A 12-person startup compiles board decks once a quarter, pulling metrics from Stripe, headcount from BambooHR, and roadmap slides from Notion. Documentero is borderline here. The 4-tool count and template metadata lookup work fine for structured sections like financials or KPIs, but board decks change format every quarter based on investor questions and narrative emphasis. You'll spend more time re-templating in Documentero's editor than you save on generation, especially since the deck only runs 4 times a year. The API key auth and signed download URLs add friction when you need to iterate with your CFO in real time. This MCP makes sense if your board deck is 80% repeatable tables and charts. If it's a storytelling document that shifts structure each quarter, stick with manual assembly in Google Slides or Pitch until the format stabilizes.

When Documentero solves repetitive export workflows under 100 tickets a month

A 4-person support team at a healthcare SaaS needs to export ticket threads as PDFs for HIPAA audit trails, averaging 60-80 tickets monthly. Documentero is the right call. You template the PDF layout once with ticket metadata fields (submitter, timestamps, message thread), then use the Generate Document tool to render each export on-demand when a ticket closes. The JSON schema validation catches missing PHI disclosures before the PDF generates, and the signed download URL gives you a 24-hour window to archive to S3 or your compliance system. The limit: if you're exporting 500+ tickets a month, the per-generation cost on Documentero's plan tiers gets expensive compared to a headless Chrome script. This works when export volume is moderate, the format is fixed by compliance requirements, and your team doesn't want to maintain a custom rendering pipeline. If you're under 100 exports monthly and the format won't change, Documentero pays for itself in avoided engineering hours.