Invoice MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMP_DIR | No | Directory for temporary files. Defaults to system temp directory. | |
| FROM_NAME | No | The name that will appear in the 'From' field. | |
| SMTP_HOST | No | SMTP server host (e.g., smtp.gmail.com). Required for email functionality. | |
| SMTP_PASS | No | SMTP password or app password. Required for email functionality. | |
| SMTP_PORT | No | SMTP server port. | 587 |
| SMTP_USER | No | SMTP username/email. Required for email functionality. | |
| FROM_EMAIL | No | The email address that will appear in the 'From' field. Defaults to SMTP_USER. | |
| OUTPUT_DIR | No | Directory where generated PDF invoices are saved. Highly recommended to set an absolute path to avoid permission issues. | ./invoices |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_invoice_pdfC | Generate a PDF invoice file |
| send_invoice_emailC | Create and send an invoice via email |
| get_invoice_templateB | Get the current invoice template structure for reference |
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 3 tools
Each tool has a clearly distinct purpose: create_invoice_pdf generates a PDF file, get_invoice_template retrieves template structure, and send_invoice_email handles email delivery. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (create_invoice_pdf, get_invoice_template, send_invoice_email) with clear verbs and descriptive nouns. The naming is uniform and predictable throughout the set.
With only 3 tools, the set feels thin for an invoice management server, lacking operations like updating, deleting, or listing invoices. While the tools cover core actions, the count is borderline low for typical domain coverage.
The tool set has significant gaps for invoice management: it includes creation, template retrieval, and email sending, but misses essential CRUD operations (e.g., list_invoices, update_invoice, delete_invoice) and other lifecycle steps like payment tracking or status updates, which could lead to agent failures in workflows.