Invoicetronic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVOICETRONIC_API_KEY | Yes | Your Invoicetronic API key for authentication. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_statusA | Get Invoicetronic account status (credits, limits, usage). |
| health_checkA | Check if the Invoicetronic API is healthy. |
| list_sent_invoicesB | List sent (outgoing) invoices. Filter by company_id, SDI identifier, VAT/fiscal code (committente/prestatore), or file_name. |
| get_sent_invoiceB | Get a sent invoice by its numeric ID. |
| get_sent_invoice_by_identifierA | Get a sent invoice by its SDI identifier string. |
| get_sent_invoice_payloadB | Get the XML payload of a sent invoice by ID. |
| send_invoice_xmlB | Send a FatturaPA XML invoice to SDI. Set validate=True to pre-validate, signature=True for digital signing. |
| validate_invoice_xmlB | Validate a FatturaPA XML invoice without sending it. |
| list_received_invoicesB | List received (incoming) invoices. Filter by company_id, SDI identifier, unread status, VAT/fiscal code. |
| get_received_invoiceB | Get a received invoice by its numeric ID. |
| get_received_invoice_payloadB | Get the XML payload of a received invoice by ID. |
| list_companiesA | List all companies configured in the Invoicetronic account. |
| get_companyC | Get a company by its numeric ID. |
| list_eventsA | List recent events/log entries from the Invoicetronic account. |
| get_eventC | Get a specific event/log entry by ID. |
| list_updatesA | List SDI status updates (notifications about invoice processing). |
| get_updateB | Get a specific SDI update by ID. |
| export_invoicesA | Export all invoices as a ZIP archive. Returns the download URL or binary info. |
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 18 tools
Each tool targets a distinct resource or action. The 'get' tools separate invoices, payloads, companies, events, and updates clearly. List tools are separated by resource type. There is no ambiguity between sent/received invoices or between metadata and payload retrieval.
Most tools follow a verb_noun pattern (get_*, list_*, send_*, validate_*, export_*). The exceptions are 'account_status' and 'health_check', which are noun-based. This minor inconsistency does not hinder understanding.
18 tools is well-scoped for an invoicing server. It covers sent and received invoice management, company lookup, event logging, SDI updates, validation, and export. The count feels appropriate without being overwhelming.
The core invoicing workflow is well-covered: send, validate, list, get, and export invoices. SDI updates and events are tracked. The only notable gap is the lack of create/update/delete operations for companies, which are limited to read-only access.