MCP Invoice Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_ENV | No | Environment (development or production) | development |
| APP_DATA_FILE | No | Path to the billing data TOML file | data/billing.toml |
| APP_OUTPUT_DIR | No | Directory where generated PDFs are saved | outputs |
| APP_SERVICE_NAME | No | Name of the MCP server | Invoice Generator Service |
| APP_TEMPLATE_DIR | No | Directory containing Typst invoice templates | templates |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_default_valuesA | Get the default values for invoices, including available issuers, services, and clients. |
| generate_invoiceB | Generate an invoice for a client in PDF format. The invoice is saved to the outputs directory and the path is returned. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves configuration defaults, the other generates the invoice. There is no overlap or confusion between them.
Both tools follow a consistent verb_noun pattern with lowercase and underscores ('get_default_values', 'generate_invoice'). The style is uniform across the set.
With only two tools, the server feels thin for an invoice generator, though the core functionality (fetching defaults and generating) is present. It falls at the lower end of acceptable tool counts.
The set covers the essential flow of retrieving defaults and generating an invoice, but lacks auxiliary operations such as listing previously generated invoices or managing invoice data. These are minor gaps that agents can work around.