Billingengine MCP vs MCP Ap2

A side-by-side look at the Billingengine MCP and MCP Ap2 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Billingengine MCP logoBillingengine MCPFinance & Fintech · Local subprocess (stdio)MCP server for BillingEngine to create and manage customers, draft invoices, e-invoices, and payments from Claude, Cursor, and other MCP clients.82ExcellentAuth: api key requiredMCP Ap2 logoMCP Ap2Finance & Fintech · Local subprocess (stdio)MCP server for AP2 — Google's Agent-to-Agent Payment Protocol (authorization, audit, trust)67GreatAuth: not declared

Verdict: choose Billingengine MCP for finance & fintech work as a local process; choose MCP Ap2 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?

Billingengine MCP logoChoose 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.
Explore Billingengine MCP

MCP Ap2 logoChoose MCP Ap2 when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_oauth_token, send_pix, create_pix_qr.
Explore MCP Ap2

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBillingengine MCP logoBillingengine MCPMCP Ap2 logoMCP Ap2
CategoryFinance & FintechFinance & Fintech
Quality signal82/100 · Excellent67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingPaid serviceNot declared
Required env varsBILLINGENGINE_API_KEYNone listed
Verified owner VerifiedCommunity listing
GitHub stars0274
Directory activity 5 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1022

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.

MCP Ap2 tools 22

  • get_oauth_tokenMint or return a cached OAuth2 client_credentials bearer token for the Itaú Developer Portal. Exposed so agents can inspect token freshness; normal tool calls obtain tokens implicitly.
  • send_pixInitiate an outbound Pix payment from the merchant's Itaú account. Amount in BRL major units (e.g. '10.50').
  • create_pix_qrCreate a dynamic Pix charge with QR code (cob). Returns the txid, copy-paste EMV payload, and location URL.
  • get_pixRetrieve a Pix transaction by its BCB endToEndId (E<ispb><yyyymmddhhmm><sequence>).
  • resolve_dict_keyResolve a DICT key (CPF, CNPJ, email, phone, EVP) to the owner's account data before sending a Pix. Subject to BCB rate limits per consenting payer.
  • refund_pixRefund (devolução) a previously received Pix. Must reference the original endToEndId and a merchant-side refund id.
  • create_boletoIssue a boleto via Itaú Cobrança. Returns nosso_numero, linha_digitável, barcode, and PDF URL.
  • get_boletoRetrieve a boleto by its Itaú identifier (id or nosso_numero).
  • cancel_boletoCancel (baixa) an outstanding boleto before payment.
  • get_statementRetrieve account statement transactions for a given period. Paginated.
  • arrecadacao_payPay a utility, tax, or concessionária bill via Itaú Arrecadação. Works with barcode (código de barras) or linha digitável.
  • create_pix_cobvCreate a Pix charge with due date (cobv) — used for boleto-like Pix where the payer can pay at or after a due date with optional fine/interest. Returns txid, copy-paste EMV payload, and location URL.
  • +10 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "billingengine-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "billingengine-mcp"
      ],
      "env": {
        "BILLINGENGINE_API_KEY": "YOUR_BILLINGENGINE_API_KEY_HERE"
      }
    }
  }
}

MCP Ap2

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-ap2": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-itau@alpha"
      ]
    }
  }
}

Frequently asked questions

Billingengine MCP is categorized under Finance & Fintech and uses a local stdio subprocess. MCP Ap2 belongs to Finance & Fintech and uses a local stdio subprocess. Pick Billingengine MCP for finance & fintech work and MCP Ap2 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. MCP Ap2 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-ap2 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. MCP Ap2 has 67/100 (Great) with 0 views, 0 installs and 274 GitHub stars.