Billingengine MCP vs Pyrimid Protocol
A side-by-side look at the Billingengine MCP and Pyrimid Protocol 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 Pyrimid Protocol 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 Pyrimid Protocol when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pyrimid_browse, pyrimid_buy, pyrimid_preview.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 79/100 · Great | 51/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 | None listed |
| 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 | 5 |
| Full listing | View Billingengine MCP | View Pyrimid Protocol |
Tools & capabilities
Billingengine MCP tools 10
find_customersSearches customers by company, name, email or identifier of another systemcreate_customerCreates a customerupdate_customerChanges a customercreate_invoiceCreates a **draft** invoice for a customerupdate_invoiceChanges a draft invoicelist_invoicesLists invoices, filtered by status, type, customer, number, identifier or dateget_invoiceReturns one invoice with items, tax breakdown and statusdownload_invoiceSaves the PDF or the XML e-invoice to your Downloads folderrecord_paymentRecords a payment for sent invoiceslist_paymentsLists payments, optionally for one invoice
Pyrimid Protocol tools 5
pyrimid_browseSearch catalog by query, price, category, verified statuspyrimid_buyPurchase a product via x402 with affiliate attributionpyrimid_previewPreview the commission split before buyingpyrimid_categoriesList all product categories with countspyrimid_register_affiliateInstructions to register as an affiliate onchain
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"
}
}
}
}
Pyrimid Protocol
{
"mcpServers": {
"pyrimid-protocol": {
"command": "npx",
"args": [
"-y",
"graph"
]
}
}
}
Frequently asked questions
Billingengine MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Pyrimid Protocol belongs to Finance & Fintech and uses a local stdio subprocess. Pick Billingengine MCP for finance & fintech work and Pyrimid Protocol 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. Pyrimid Protocol 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 pyrimid-protocol 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 79/100 (Great) with 5 views, 0 installs and 0 GitHub stars. Pyrimid Protocol has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.