Billingengine MCP vs SumUp MCP Server
A side-by-side look at the Billingengine MCP and SumUp 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 SumUp 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 SumUp 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:
SUMUP_API_KEY. - You want tools like
create_checkout, create_customer, create_merchant_member.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 82/100 · Excellent | 64/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 | SUMUP_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 0 | 14 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | 36 |
| Full listing | View Billingengine MCP | View SumUp 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.
SumUp MCP Server tools 36
create_checkoutCreates a new payment checkout resource. The unique `checkout_reference` created by this request, is used for further manipulation of the checkout. For 3DS checkouts, add the `redirect_url` parameter to your request body schema. To use the [Hosted Checkout](https://developer.sumup.com/online-payments/checkouts/hosted-checkout/) page, set the `hosted_checkout.enabled` to `true`. Follow by processing a checkout to charge the provided payment instrument.create_customerCreates a new saved customer resource which you can later manipulate and save payment instruments to.create_merchant_memberCreate a merchant member.create_merchant_roleCreate a custom role for the merchant. Roles are defined by the set of permissions that they grant to the members that they are assigned to.create_readerCreate a new Reader for the merchant account.create_reader_checkoutCreates a Checkout for a Reader. This process is asynchronous and the actual transaction may take some time to be started on the device. There are some caveats when using this endpoint: * The target device must be online, otherwise checkout won't be accepted * After the checkout is accepted, the system has 60 seconds to start the payment on the target device. During this time, any other checkout for the same device will be rejected. **Note**: If the target device is a Solo, it must be in version 3.3.24.3 or higher.create_reader_terminateTerminate a Reader Checkout stops the current transaction on the target device. This process is asynchronous and the actual termination may take some time to be performed on the device. There are some caveats when using this endpoint: * The target device must be online, otherwise terminate won't be accepted * The action will succeed only if the device is waiting for cardholder action: e.g: waiting for card, waiting for PIN, etc. * There is no confirmation of the termination. If a transaction is successfully terminated and `return_url` was provided on Checkout, the transaction status will be sent as `failed` to the provided URL. **Note**: If the target device is a Solo, it must be in version 3.3.28.0 or higher.deactivate_checkoutDeactivates an identified checkout resource. If the checkout has already been processed it can not be deactivated.deactivate_payment_instrumentDeactivates an identified card payment instrument resource for a customer.delete_merchant_memberDeletes a merchant member.delete_merchant_roleDelete a custom role.delete_readerDelete a reader.- +24 more on the listing page
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"
}
}
}
}
SumUp MCP Server
{
"mcpServers": {
"sumup-mcp-server": {
"command": "npx",
"args": [
"-y",
"@sumup/mcp"
],
"env": {
"SUMUP_API_KEY": "YOUR_SUMUP_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Billingengine MCP is categorized under Finance & Fintech and uses a local stdio subprocess. SumUp MCP Server belongs to Finance & Fintech and uses a local stdio subprocess. Pick Billingengine MCP for finance & fintech work and SumUp 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. SumUp 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 sumup-mcp-server 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. SumUp MCP Server has 64/100 (Good) with 0 views, 0 installs and 14 GitHub stars.