Skip to main content
Glama
BillingEngine MCP server

BillingEngine MCP server

Official

BillingEngine MCP server

AllMCPs Verified

Create customers and invoices, look up open invoices and record payments in BillingEngine by talking to Claude, Cursor or any other MCP client:

"Create an invoice for Acme Painting over 100 euros."

"Which invoices are overdue?"

"Acme paid invoice 2610030028, record the payment."

BillingEngine is invoicing software for freelancers and small businesses with e-invoicing (EN 16931, XRechnung, ZUGFeRD / Factur-X). The server is a thin layer over the BillingEngine API and runs on your computer.

Requirements

  • Node.js 20 or newer

  • A BillingEngine account on a paid plan. The API is not available in the Free plan.

  • Your API key from Settings > API keys in BillingEngine

Related MCP server: InvoiceBloom MCP server

Setup

Claude Desktop

Add this to claude_desktop_config.json:

{
  "mcpServers": {
    "billingengine": {
      "command": "npx",
      "args": ["-y", "billingengine-mcp"],
      "env": { "BILLINGENGINE_API_KEY": "your-api-key" }
    }
  }
}

Claude Code

claude mcp add billingengine --env BILLINGENGINE_API_KEY=your-api-key -- npx -y billingengine-mcp

Cursor and other clients

Use the same command, args and env as above in the MCP settings of your client.

Tools

Tool

What it does

find_customers

Searches customers by company, name, email or identifier of another system

create_customer

Creates a customer

update_customer

Changes a customer

create_invoice

Creates a draft invoice for a customer

update_invoice

Changes a draft invoice

list_invoices

Lists invoices, filtered by status, type, customer, number, identifier or date

get_invoice

Returns one invoice with items, tax breakdown and status

download_invoice

Saves the PDF or the XML e-invoice to your Downloads folder

record_payment

Records a payment for sent invoices

list_payments

Lists payments, optionally for one invoice

What it does and does not do

  • Invoices are created as drafts. Nothing is sent to your customers; you review and send the invoice in BillingEngine. Every result contains a link to open the draft.

  • Prices are net or gross, as set in your account; every invoice says which. Amounts in results are decimal strings such as "119.00". Number, language, texts, VAT treatment and payment terms come from your account settings, exactly as in the invoice form.

  • Nothing can be deleted through this server.

  • New invoices count towards the monthly invoice maximum of your plan.

  • The API allows 60 requests per minute per key.

  • Your key stays on your computer and is only sent to BillingEngine.

If a key is ever exposed, create a new one under Settings > API keys. The old key stops working immediately. The settings also show when the key was last used.

Configuration

Variable

Meaning

BILLINGENGINE_API_KEY

Your API key (required)

BILLINGENGINE_URL

Base URL, defaults to https://www.billingengine.com

Development

npm install
npm run build
BILLINGENGINE_API_KEY=... node dist/index.js

License

MIT. BillingEngine itself is a commercial service; see billingengine.com.

Available Tools

10 tools
create_customerCreate a customerA

Creates a customer. Needs a company or a last name and a full address (line 1, postal code, city, country).

Inputs: address (required), email, phone, company, +4 more. Returns: object

create_invoiceCreate a draft 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.

Inputs: items (required), customer_id (required), date, due_days, +4 more. Returns: object

download_invoiceDownload an invoice fileA
Idempotent

Saves the PDF or the XML e-invoice of an invoice on this computer and returns the file path. Defaults to the Downloads folder.

Inputs: id (required), format, directory. Returns: object

find_customersFind customersA
Read-only

Lists customers, optionally filtered by a search text that matches company, names and email.

Inputs: page, query. Returns: object

get_invoiceGet an invoiceB
Read-only

Returns one invoice with its items, amounts and payment status.

Inputs: id (required). Returns: object

list_invoicesList invoicesB
Read-only

Lists invoices, newest first. Status: draft, open (sent and unpaid), overdue (open and past due) or paid.

Inputs: page, after, before, number, +3 more. Returns: object

list_paymentsList paymentsA
Read-only

Lists recorded payments, newest first, optionally only those for one invoice.

Inputs: page, invoice_id. Returns: object

record_paymentRecord a paymentA

Records a payment for one or more sent, open invoices of the same customer and tax rate. The amount is gross.

Inputs: amount (required), invoice_ids (required), date, payment_method. Returns: object

update_customerUpdate a customerA
Idempotent

Changes the given fields of a customer; fields that are left out stay as they are.

Inputs: id (required), email, phone, address, +5 more. Returns: object

update_invoiceUpdate a draft invoiceA
Idempotent

Changes a draft invoice. Passing items replaces all existing items, so send the complete list. Sent invoices cannot be changed.

Inputs: id (required), date, items, due_days, +4 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes French electronic invoicing as a local stdio MCP server, letting an AI client create EN 16931-compliant Factur-X invoices with guaranteed legal numbering, client and organization management, and invoice history. It can also submit a generated invoice to a French e-invoicing platform (PDP) after explicit confirmation.
      5
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude and other MCP clients to manage a small-business back office, including clients, quotes, invoices, payments, reports, and PDF invoice export, while keeping data in a local SQLite file.
      21
      MIT