Billingengine MCP vs BillingServ MCP Server
A side-by-side look at the Billingengine MCP and BillingServ MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Billingengine MCP for finance & fintech work as a local process; choose BillingServ MCP Server for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Billingengine MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
BILLINGENGINE_API_KEY. - You want tools like
find_customers, create_customer, update_customer.
Choose BillingServ MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BILLINGSERV_API_BASE_URL, BILLINGSERV_API_KEY, BILLINGSERV_TIMEOUT_MS. - You want tools like
billingserv_list_endpoints, billingserv_get, billingserv_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 82/100 · Excellent | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | BILLINGENGINE_API_KEY | BILLINGSERV_API_BASE_URLBILLINGSERV_API_KEYBILLINGSERV_TIMEOUT_MS |
| Verified owner | Verified | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | 3 |
| Full listing | View Billingengine MCP | View BillingServ MCP Server |
Tools & capabilities
Billingengine MCP tools 10
find_customersLists customers, optionally filtered by a search text that matches company, names and email.create_customerCreates a customer. Needs a company or a last name and a full address (line 1, postal code, city, country).update_customerChanges the given fields of a customer; fields that are left out stay as they are.create_invoiceCreates 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_invoiceChanges a draft invoice. Passing items replaces all existing items, so send the complete list. Sent invoices cannot be changed.list_invoicesLists invoices, newest first. Status: draft, open (sent and unpaid), overdue (open and past due), paid, uncollectible or cancelled. Type: invoice or credit_note.get_invoiceReturns one invoice with its items, tax breakdown, amounts and status. Amounts are decimal strings such as "119.00".download_invoiceSaves the PDF or the XML e-invoice of an invoice on this computer and returns the file path. Defaults to the Downloads folder.record_paymentRecords a payment for one or more sent, open invoices of the same customer and tax rate. The amount is gross.list_paymentsLists recorded payments, newest first, optionally only those for one invoice.
BillingServ MCP Server tools 3
billingserv_list_endpointsLists every BillingServ endpoint the server can call, along with descriptions, required parameters, and valid values. Assistants usually call this first to see what data is available.billingserv_getCalls one allowlisted BillingServ API v2 `GET` endpoint.billingserv_createCreates or updates records through an allowlisted set of `POST` endpoints. It also activates, validates, and deactivates software licenses. This is the tool to gate behind approval in your MCP client if you want a confirmation step before anything changes.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Billingengine MCP
{
"mcpServers": {
"billingengine-mcp": {
"command": "npx",
"args": [
"-y",
"billingengine-mcp"
],
"env": {
"BILLINGENGINE_API_KEY": "YOUR_BILLINGENGINE_API_KEY_HERE"
}
}
}
}
BillingServ MCP Server
{
"mcpServers": {
"mcp-64": {
"command": "npx",
"args": [
"-y",
"@billingserv/mcp-server"
],
"env": {
"BILLINGSERV_API_BASE_URL": "YOUR_BILLINGSERV_API_BASE_URL_HERE",
"BILLINGSERV_API_KEY": "YOUR_BILLINGSERV_API_KEY_HERE",
"BILLINGSERV_TIMEOUT_MS": "YOUR_BILLINGSERV_TIMEOUT_MS_HERE"
}
}
}
}
Frequently asked questions
Billingengine MCP is categorized under Finance & Fintech and uses a local stdio subprocess. BillingServ MCP Server belongs to Finance & Fintech and uses a local stdio subprocess. Pick Billingengine MCP for finance & fintech work and BillingServ MCP Server for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Billingengine MCP is listed as a paid service. Auth: api key required. BillingServ MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add billingengine-mcp and mcp-64 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Billingengine MCP has a quality signal of 82/100 (Excellent) with 5 views, 0 installs and 0 GitHub stars. BillingServ MCP Server has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.