Pix Bcb MCP server
MCP server for Pix BCB API — official Banco Central do Brasil Pix standard
271 stars
Reviews
Write oneNobody has reviewed Pix Bcb yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Pix Bcb tools (18, 7 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
create_cobwrite actionCreate an immediate Pix charge (cobranca imediata)
create_cobvwrite actionCreate a due-date Pix charge (cobranca com vencimento)
create_devolucaowrite actionRequest a refund (devolução) for a received Pix (PUT /pix/{e2eid}/devolucao/{id})
create_pix_keywrite actionRegister a Pix key in DICT (requires PSP support)
delete_webhookwrite actionRemove the webhook configured for a Pix key (DELETE /webhook/{chave})
get_cobGet immediate charge details by txid
get_devolucaoGet refund details by e2eid + refund id (GET /pix/{e2eid}/devolucao/{id})
get_pixGet a received Pix payment by e2eid (endToEndId)
get_pix_keyLook up a Pix key in DICT
list_cobsList immediate charges with date range and filters
list_cobvList due-date charges (cobv) within a date range
list_pix_keysList all Pix keys owned by the authenticated account at this PSP
list_pix_receivedList received Pix payments within a date range
request_key_portabilityRequest portability of a Pix key from another PSP into this PSP (DICT portability flow)
resolve_key_claimResolve a pending DICT key claim (confirm or cancel) — POST /dict/keys/claims/{id}/resolve
set_webhookConfigure a webhook URL for a given Pix key (PUT /webhook/{chave}). PSP will POST notifications when Pix payments arrive.
update_cobwrite actionRevise an existing immediate charge (PATCH /cob/{txid}). Common updates: status REMOVIDA_PELO_USUARIO_RECEBEDOR to cancel, or change valor/solicitacaoPagador.
update_cobvwrite actionRevise an existing due-date charge (PATCH /cobv/{txid})
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 29 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Pix Bcb compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 18
- the typical server has 7
- Tools that change things
- 39%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 271
- more than 95% of 28,688 servers
What its tools let an agent do: 10 read · 4 create · 3 change · 1 delete
Install Pix Bcb in Claude Code, Cursor or VS Code
Runs npx -y @codespar/mcp-pix-bcb on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-pix-bcb -- npx -y @codespar/mcp-pix-bcb
What the publisher says
From the Pix Bcb repository's README, as published. We do not edit it. Read it on GitHub
MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute
The Problem
AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).
Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.
MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.
The Solution
Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.
🛒 Customer places order
→ 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
→ 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
→ 📦 Agent generates shipping label (Melhor Envio / Skydropx)
→ 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
→ 📊 Agent records in ERP (Omie / Bling / Tiny)
→ 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)Six systems. Zero human intervention. One agent.
Agentic Payment Protocols
Four servers for the emerging agentic payment stack:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Pix Bcb: common questions
- Is Pix Bcb MCP server safe?
- Mostly: it is graded B (82/100). Read the Pix Bcb safety report
- How do I install Pix Bcb?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Pix Bcb need an API key?
- Yes. The registry entry asks for
PIX_CLIENT_SECRET. - Is Pix Bcb maintained?
- The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
- How does Pix Bcb compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 18 (the typical server has 7); tools that change things 39% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.