BillingEngine MCP
Use an MCP client to find customers, prepare draft invoices and record payments in BillingEngine. The local server requires Node.js 20+, a paid BillingEngine plan and an API key.
Start with the current requirements ↓What it helps you do
This integration is useful for freelancers and small teams that already invoice in BillingEngine. The tools can find, create and update customers, list invoices, retrieve invoice details, download PDF/XML files and create or edit invoice drafts.
Draft invoices are not automatically sent to customers. Review and send them in BillingEngine. record_payment records an existing payment against an invoice; it does not initiate a bank transfer. The documented server does not expose deletion operations.
Costs and access requirements
The BillingEngine Free plan does not include API access. You need a paid plan and its API key. New invoices count toward that plan's monthly invoice maximum; the documented API limit is 60 requests per minute per key. The MCP code is MIT-licensed, while BillingEngine is a commercial service. Check the official MCP requirements and project README for current eligibility and plan terms.
Documented setup
Install Node.js 20 or newer and obtain an API key from BillingEngine Settings → API keys. A local stdio-capable MCP client can launch:
Command: npx
Arguments: -y billingengine-mcp
Environment: BILLINGENGINE_API_KEY=YOUR_API_KEY
Store the real key in your client's protected environment settings. The server runs locally and calls the BillingEngine API; it is not an offline invoicing database.
Check your first result
Start by listing invoices or finding a known customer. Before allowing a write, confirm the customer, currency, amount and whether the account uses net or gross prices. If you create a draft, open its returned link and check the line items and tax settings in BillingEngine.
This can change real business records. Check an existing invoice before retrying an uncertain write to avoid duplicates. For authentication or rate-limit errors, inspect key permissions and request frequency. API documentation.
What this listing covers
This is a free editorial listing based on public documentation and source inspection, not a security certification or a hands-on product review. Your AI client can have separate subscription or model usage charges. Check the linked product terms before connecting an account or running billable work.
Primary sources
Source-checked 2026-10-22. Published documentation, account availability and hands-on behavior are separate evidence. Examples and checklists here are editorial material.