MCP Ap2 vs SumUp MCP Server
A side-by-side look at the MCP Ap2 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 MCP Ap2 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 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.
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 | 67/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | SUMUP_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 274 | 14 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 22 | 36 |
| Full listing | View MCP Ap2 | View SumUp MCP Server |
Tools & capabilities
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
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.
MCP Ap2
{
"mcpServers": {
"mcp-ap2": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-itau@alpha"
]
}
}
}
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
MCP Ap2 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 MCP Ap2 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.
MCP Ap2 has no declared pricing — check the project's own site. 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 mcp-ap2 and sumup-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Ap2 has a quality signal of 67/100 (Great) with 0 views, 0 installs and 274 GitHub stars. SumUp MCP Server has 64/100 (Good) with 0 views, 0 installs and 14 GitHub stars.