invovate-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVOVATE_API_KEY | No | Free API key (inv_…). Enables PDF/UBL output and hosted links. | |
| INVOVATE_API_BASE | No | Override the API base (rarely needed). | https://invovate.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_invoice_totalsA | Compute invoice totals (subtotal, per-line and global discounts, tax, shipping, deposit, grand total, balance due) without rendering a file. No API key required. Use this to validate amounts before generating a PDF. |
| generate_invoice_pdfA | Generate a PDF invoice. By default returns a shareable 7-day hosted link that renders the PDF (best for chat — give the link to the user). If save_path is provided, the binary PDF is written to that local file instead. Set INVOVATE_API_KEY (free) for reliable PDF output. |
| generate_invoice_ublA | Generate a UBL 2.1 XML invoice (for interoperability/archival — NOT a regulated e-invoice transmission; no Peppol/Factur-X/XRechnung compliance). Returns the XML as text. Requires INVOVATE_API_KEY. |
| get_invoice_capabilitiesA | List what the Invovate invoice API supports: languages, PDF templates, and notable features. Use this to pick valid language/template/currency values. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: calculating totals, generating PDF, generating UBL XML, and retrieving capabilities. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., generate_invoice_pdf, get_invoice_capabilities). The convention is uniform and predictable.
With 4 tools covering calculation, PDF generation, UBL generation, and capabilities, the scope is well-targeted for an invoice generation server. Each tool serves a necessary purpose without bloat.
The tool set covers the core invoice generation workflow (validation, PDF, UBL, capabilities). Missing are retrieval or management of previously generated invoices, but these are arguably outside the stated scope.