simple_invoicing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVOICING_BASE_URL | Yes | The base URL of the simple_invoicing FastAPI instance | |
| INVOICING_API_TOKEN | Yes | A long-lived bearer token (API token) for the backend |
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 |
|---|---|
| list_invoicesC | List all invoices with optional filtering |
| get_invoiceA | Get a single invoice by ID |
| create_invoiceC | Create a new invoice |
| get_invoice_pdfA | Get the PDF for an invoice (returns base64 if available) |
| list_productsC | List all products |
| get_productB | Get a single product by ID |
| create_productC | Create a new product |
| list_ledgersC | List all ledgers |
| get_ledger_statementB | Get the statement for a ledger with optional date range |
| get_day_bookC | Get the day book entries with optional date range |
| list_inventoryC | List all inventory items |
| list_buyersC | List all buyers |
| get_buyerB | Get a single buyer by ID |
| list_paymentsC | List all payments |
| create_paymentD | Create a new payment |
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 15 tools
Each tool targets a distinct resource (invoice, payment, product, buyer, ledger, inventory) with unique operations (create, get, list). No two tools have overlapping purposes, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern (e.g., create_invoice, get_buyer, list_invoices) using lowercase snake_case. No mixing of conventions or vague verbs like 'process' or 'do_thing'.
With 15 tools, the surface is well-scoped for a simple invoicing system covering core entities (invoices, payments, products, buyers, ledgers, inventory). Each tool earns its place without unnecessary bloat or deficiency.
The tool set provides basic CRUD operations (create and read/list) for most entities but lacks update and delete functionalities (e.g., update_invoice, delete_product). While the core workflow of creating and reading is covered, agents may hit dead ends when needing to modify or remove records.