A side-by-side look at the Billingengine MCP and Phantom 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 Phantom MCP Server for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
BILLINGENGINE_API_KEY.find_customers, create_customer, update_customer.PHANTOM_API_KEY, PHANTOM_API_URL, PHANTOM_PAYER_PRIVATE_KEY, PHANTOM_ROUTER_ADDRESS, PHANTOM_ALLOW_CUSTOM_API_URL.quote_payment, authorize_payment, submit_payment.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 79/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Paid service | Not declared |
| Required env vars | BILLINGENGINE_API_KEY | PHANTOM_API_KEYPHANTOM_API_URLPHANTOM_PAYER_PRIVATE_KEYPHANTOM_ROUTER_ADDRESSPHANTOM_ALLOW_CUSTOM_API_URL |
| Verified owner | Verified | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | 4 |
| Full listing | View Billingengine MCP | View Phantom MCP Server |
find_customersSearches customers by company, name or emailcreate_customerCreates a customerupdate_customerChanges a customercreate_invoiceCreates a **draft** invoice for a customerupdate_invoiceChanges a draft invoicelist_invoicesLists invoices, filtered by status, customer, number or dateget_invoiceReturns one invoice with items and payment statusdownload_invoiceSaves the PDF or the XML e-invoice to your Downloads folderrecord_paymentRecords a payment for sent invoiceslist_paymentsLists payments, optionally for one invoicequote_payment```jsonauthorize_payment```jsonsubmit_payment```jsonverify_payment```jsonPaste 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.
{
"mcpServers": {
"billingengine-mcp": {
"command": "npx",
"args": [
"-y",
"billingengine-mcp"
],
"env": {
"BILLINGENGINE_API_KEY": "YOUR_BILLINGENGINE_API_KEY_HERE"
}
}
}
}
{
"mcpServers": {
"phantom-mcp-server-2": {
"command": "npx",
"args": [
"@phantomid/mcp-server"
],
"env": {
"PHANTOM_API_KEY": "YOUR_PHANTOM_API_KEY_HERE",
"PHANTOM_API_URL": "YOUR_PHANTOM_API_URL_HERE",
"PHANTOM_PAYER_PRIVATE_KEY": "YOUR_PHANTOM_PAYER_PRIVATE_KEY_HERE",
"PHANTOM_ROUTER_ADDRESS": "YOUR_PHANTOM_ROUTER_ADDRESS_HERE",
"PHANTOM_ALLOW_CUSTOM_API_URL": "YOUR_PHANTOM_ALLOW_CUSTOM_API_URL_HERE"
}
}
}
}