Billingengine MCP vs CCXT
A side-by-side look at the Billingengine MCP and CCXT 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 CCXT for finance & fintech. 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 CCXT when
- You need dedicated capabilities in the Finance & Fintech domain.
- You want tools like
list_exchanges, describe_exchange, describe_method.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 79/100 · Great | 64/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | 44,480 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 10 | 32 |
| Full listing | View Billingengine MCP | View CCXT |
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
CCXT tools 32
list_exchangesList every exchange this server supports (built from ccxt.exchanges at runtime), with name, websocket and prediction-market availability. Filter by a name query or by support for a unified method.describe_exchangeOne exchange's supported unified methods, market types, timeframes, required credential fields, sandbox availability and documentation URLs. Per-method detail lives in describe_method.describe_methodSearch unified method names by keyword, or get one method's signature and parameter documentation. With "exchange" it adds that exchange's own docs (including supported params.* keys and links to the exchange API reference), per-market-type feature support, and searches its implicit (exchange-specific) endpoints too. Full ccxt manual: https://docs.ccxt.com/search_marketsSearch and filter the markets of one exchange (by text, base, quote, settle currency, market type), paginated. Use this to resolve unified symbols — there is deliberately no list-all-markets tool. On prediction exchanges use search_events instead.get_tickers24h price tickers for one or more unified symbols on an exchange (outcome handles on prediction exchanges).get_orderbookCurrent order book (bids and asks) for one unified symbol.get_ohlcvHistorical OHLCV candlestick data for a symbol and timeframe. Rows are [timestampMs, open, high, low, close, volume]. Page back with "since"; "params.until" bounds the end.get_tradesRecent public trades for one unified symbol.search_eventsSearch events on a prediction-market exchange (polymarket, kalshi, limitless, myriad, hyperliquid with prediction=true). A scoping filter is required: query, tags, or params.eventId/params.slug. Returns events with their markets and outcome handles — outcome handles are what you pass as the symbol to get_tickers/get_orderbook/create_order on prediction exchanges.call_read_methodEscape hatch covering every unified read method not served by a dedicated tool (fetchFundingRate, fetchLedger, fetchOpenInterest, fetchLiquidations, fetchEvent, fetchSettlements, …). Only fetch*/load* methods are accepted — writes are structurally rejected. Get the signature first with describe_method. Docs: https://docs.ccxt.com/call_implicit_getCall an exchange-specific implicit REST endpoint over HTTP GET, for data the unified API does not cover. Pass the implicit method name in the "method" argument (e.g. "publicGetTickerPrice"); these are exchange-specific — find them with describe_method {"query": ..., "exchange": ...} (its results list the name to pass here). The response is the raw exchange payload. Consult the exchange API reference (describe_exchange .urls.doc) and the ccxt manual: https://docs.ccxt.com/get_safety_statusWhat this server is currently allowed to do: configured accounts (names only — never credentials), enabled capability tiers, caps, sandbox/live environments, journal location, unresolved order intents, and any configuration problems.- +20 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"
}
}
}
}
CCXT
No confirmed install command for CCXT yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Billingengine MCP is categorized under Finance & Fintech and uses a local stdio subprocess. CCXT belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick Billingengine MCP for finance & fintech work and CCXT 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. CCXT has no confirmed install command yet — follow its own setup instructions.
Billingengine MCP is listed as a paid service. Auth: api key required. CCXT 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 ccxt 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. CCXT has 64/100 (Good) with 2 views, 0 installs and 44,480 GitHub stars.