BillingEngine MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BILLINGENGINE_URL | No | Base URL for the BillingEngine API. | https://www.billingengine.com |
| BILLINGENGINE_API_KEY | Yes | Your BillingEngine API key from Settings > API. Required to authenticate with the BillingEngine API. |
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 |
|---|---|
| find_customersA | Lists customers, optionally filtered by a search text that matches company, names and email. |
| create_customerA | Creates a customer. Needs a company or a last name and a full address (line 1, postal code, city, country). |
| update_customerA | Changes the given fields of a customer; fields that are left out stay as they are. |
| create_invoiceA | Creates a draft invoice for a customer. Number, language, texts and VAT treatment come from the account settings. The invoice is not sent; it counts towards the monthly invoice maximum of the plan. |
| update_invoiceA | Changes a draft invoice. Passing items replaces all existing items, so send the complete list. Sent invoices cannot be changed. |
| list_invoicesB | Lists invoices, newest first. Status: draft, open (sent and unpaid), overdue (open and past due) or paid. |
| get_invoiceB | Returns one invoice with its items, amounts and payment status. |
| download_invoiceA | Saves the PDF or the XML e-invoice of an invoice on this computer and returns the file path. Defaults to the Downloads folder. |
| record_paymentA | Records a payment for one or more sent, open invoices of the same customer and tax rate. The amount is gross. |
| list_paymentsA | Lists recorded payments, newest first, optionally only those for one invoice. |
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 10 tools
Each tool targets a clearly distinct resource and action: customers (find/create/update), invoices (create/update/list/get/download), and payments (record/list). There is no meaningful overlap between tools, and an agent can easily select the right one based on the requested resource and operation.
All tools use snake_case with a verb_noun pattern, which is highly consistent. The only minor deviation is using 'find_customers' for listing customers while invoices and payments use 'list_*', but this does not create confusion.
With 10 tools, the set is well-scoped for a billing engine, covering the core customer, invoice, and payment operations without excessive bloat. Each tool has a clear place in the domain.
The surface covers create/read/update for customers and invoices plus payment recording, but it lacks a tool to send a draft invoice, which is a critical step because record_payment only works on sent/open invoices. Deletion operations for any entity are also absent, creating notable workflow gaps.