# mcp-ap2 [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/codespar/mcp-dev-brasil  
**GitHub Stars:** 274  
**npm Downloads (last month):** 134  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-ap2

## Description
MCP server for AP2 — Google's Agent-to-Agent Payment Protocol (authorization, audit, trust)

## Tools
Capabilities this server exposes over MCP:

- **get_oauth_token** — Mint 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_pix** — Initiate an outbound Pix payment from the merchant's Itaú account. Amount in BRL major units (e.g. '10.50').
- **create_pix_qr** — Create a dynamic Pix charge with QR code (cob). Returns the txid, copy-paste EMV payload, and location URL.
- **get_pix** — Retrieve a Pix transaction by its BCB endToEndId (E<ispb><yyyymmddhhmm><sequence>).
- **resolve_dict_key** — Resolve 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_pix** — Refund (devolução) a previously received Pix. Must reference the original endToEndId and a merchant-side refund id.
- **create_boleto** — Issue a boleto via Itaú Cobrança. Returns nosso_numero, linha_digitável, barcode, and PDF URL.
- **get_boleto** — Retrieve a boleto by its Itaú identifier (id or nosso_numero).
- **cancel_boleto** — Cancel (baixa) an outstanding boleto before payment.
- **get_statement** — Retrieve account statement transactions for a given period. Paginated.
- **arrecadacao_pay** — Pay a utility, tax, or concessionária bill via Itaú Arrecadação. Works with barcode (código de barras) or linha digitável.
- **create_pix_cobv** — Create 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.
- **list_pix_charges** — List immediate Pix charges (cob) registered by the merchant within a date range. Paginated per BACEN Pix v2.
- **register_pix_key** — Register a DICT key (CPF, CNPJ, email, phone, or EVP) on an Itaú account owned by the merchant. Subject to BCB validation flows (e.g. email/SMS confirmation for email/phone keys).
- **delete_pix_key** — Delete a DICT key owned by the merchant. Irreversible — the key becomes available for re-registration by any PSP after BCB lockout window.
- **list_pix_keys** — List DICT keys currently registered to the merchant's Itaú accounts.
- **get_boleto_pdf** — Download the PDF of an issued boleto. Returns the document as base64 (content-type application/pdf).
- **send_ted** — Send a TED transfer to an account at another bank. Same-day settlement within banking hours; otherwise queued.
- **transfer_between_accounts** — TAA — transfer between two Itaú accounts (owned by the merchant or a counterparty). Instant settlement, no BCB fee.
- **get_tariffs** — Query the tariff schedule applicable to the merchant's active contracts (Pix per-transaction, boleto registration, TED, arrecadação, etc.).
- **list_dda_bills** — List bills registered for the merchant under the DDA (Débito Direto Autorizado) enrolment. Returns pending boletos/concessionária bills the merchant has opted in to.
- **schedule_payment** — Schedule a future-dated payment (Pix, boleto, arrecadação, or TED). Itaú executes the debit on the scheduled date at D+0 cut-off.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-ap2": {
    "command": "npx",
    "args": ["-y","@codespar/mcp-itau@alpha"]
  }
}
```

## Documentation

## What mcp-ap2 does

The mcp-ap2 MCP server exposes Google's Agent-to-Agent Payment Protocol through an MCP interface. Its 22 tools cover the protocol's authorization model, audit records, and limits on how much an agent may spend or what actions it may take. This places the server in the authorization layer of an agentic commerce stack rather than in the settlement layer.

AP2 is presented alongside checkout protocols such as Stripe ACP and Google UCP, and settlement mechanisms such as x402, Pix, and card payments. In that model, the mcp-ap2 MCP server can represent the policy and traceability side of an agent payment flow while another system handles checkout or payment settlement.

## How it works

An MCP client connects to the package and invokes its AP2-related tools. Those tools are organized around three concrete concerns: authorizing agent actions, recording or reviewing audit trails, and applying scoped spending limits.

The package is described as an alpha implementation. AP2 is also described as an open specification rather than an API hosted by Google. This distinction matters when evaluating the server: MCP provides the tool interface, while the underlying AP2 service availability remains a separate concern.

## Setup and configuration

The repository identifies the package as `@codespar/mcp-ap2`. An MCP client can run packages from this collection with `npx`; the repository's alpha-package convention uses an `@alpha` install tag for alpha releases. Confirm the published package and release tag before adding it to a client configuration because the AP2 package is deprecated.

Do not assume that credentials, a base URL, or a sandbox setting are available without checking the package's own documentation.

## Tools and capabilities

- Provides 22 MCP tools for the AP2 package.
- Supports authorization concepts for agent-to-agent payments.
- Covers audit trails for payment-related agent activity.
- Applies scoped spending limits to agent actions.
- Fits the authorization layer between agent-facing commerce workflows and payment settlement rails.

## Limitations and notes

The mcp-ap2 MCP server is marked alpha and deprecated in the repository. The listed default host is `ap2.googleapis.com`; the sandbox host is `sandbox.ap2.googleapis.com`. Measurements recorded in the README found a generic HTTP 404 response from the default host and a TLS failure from the sandbox host. The repository concludes that AP2 has no live endpoint available through this package.

The package remains in the repository for reference and is excluded from its quick-start flow.

The mcp-ap2 MCP server should therefore be evaluated as an alpha reference or prototyping component.

_Full upstream README: https://allmcps.com/mcp/mcp-ap2/readme_