PagBrasil

@codespar/mcp-pagbrasil · v0.1.0

🇧🇷 BrazilPaymentsAuth · API Keybeta3 tools3 env vars

Cross-border acquirer for international merchants selling into Brazil: Pix, Automatic Pix (PagStream) and boleto without a local entity.

Get started · free View docs

MIT · runs locally or through the CodeSpar runtime

Limitations

The npm package ships no server.json manifest.

DetailsSource on GitHub

Package: @codespar/mcp-pagbrasil
Version: 0.1.0
npm dist-tag: latest
Category: Payments
Auth: API Key
Country: 🇧🇷 Brazil
License: MIT
Transport: stdio

npm GitHub Server catalog docs

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, or through the hosted runtime.

Add the server to your clientOne config entry. No build step, no SDK required.

Set the environment variables3 variables read by this server's code, listed below.

Restart and make the first callThe agent can call any of the 3 tools. Try create_order first.

Hosted MCP Build your own server

terminal

# Claude Code
claude mcp add pagbrasil -e PAGBRASIL_BASE_URL=… -e PAGBRASIL_PBTOKEN=… -e PAGBRASIL_SECRET=… -- npx -y @codespar/mcp-pagbrasil@0.1.0
# then: /mcp to confirm the server is connected

Environment variables3 variables

PAGBRASIL_BASE_URLAPI base URL. Defaults to https://sandbox.pagbrasil.com/api; production hosts are issued per-merchant.optional

PAGBRASIL_PBTOKENMerchant token (pbtoken) from the PagBrasil Dashboardrequiredsecret

PAGBRASIL_SECRETSecret phrase from the PagBrasil Dashboardrequiredsecret

Names read from the package code (@codespar/mcp-pagbrasil@0.1.0). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials. On the CodeSpar runtime the credential you connect is stored encrypted (AES-256-GCM, key derived per organization), and the runtime adds it to the provider call itself; the agent never receives it.

First call democreate_order

"Create an order / request a payment"

tools/callcreate_orderresult returned

Tools

What your agent can call.

3 tools, as the package's tools/list returns them.

create_order

Create an order / request a payment (POST /order/add, form-urlencoded). payment_type selects the method (pix | boleto | creditcard). Returns XML: for Pix it carries pix_code (copy-paste) and pix_image; for boleto, the bar code and PDF URL. order_number must be unique per customer_taxid.

get_order

Request information about an order (POST /order/get). Returns the same XML order shape as create_order, including current payment status — poll this to detect Pix/boleto settlement.

refund_order

Request a refund for a settled order (POST /order/refund). Pass amount_brl for a partial refund; omit for a full refund.

Names and descriptions come from the package's tools/list (@codespar/mcp-pagbrasil@0.1.0). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

Through the CodeSpar runtime, codespar_discover finds this server's tools, and a tools/call runs with the credential connected in your project, a test key included.

hostedhttps://connect.codespar.dev/mcp15 meta-tools

Protocol

Any MCP client

stdio

Questions

Before you install.

How do I install the PagBrasil MCP server?

Run npx -y @codespar/mcp-pagbrasil@0.1.0 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required. Prefer hosted? Add the CodeSpar endpoint with a test key and connect PagBrasil in your project; codespar_discover finds its tools.

What can my agent do with PagBrasil?

PagBrasil exposes 3 tools for payments. Your agent calls them directly; the full list is above.

How does PagBrasil authenticate, and how are credentials stored?

PagBrasil uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables. On the CodeSpar runtime the credential you connect is stored encrypted for your organization, and the runtime adds it to each provider call, so the agent never handles it.

How does PagBrasil handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.1.0, the version whose tools are listed here; your agent keeps running it until you change the version.

Is PagBrasil open source? How do I report a bug?

Yes. PagBrasil is MIT-licensed and published on npm as @codespar/mcp-pagbrasil, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Pairs well with

Payments · same category.

Zoop

@codespar/mcp-zoop · 28 tools

Brazilian payments infrastructure: Pix, boleto, card and native split of receivables. Your agent creates charges, reconciles settlements, and splits payouts across partners — in a single MCP call.

Open

Asaas

@codespar/mcp-asaas · 24 tools

Billing automation, Pix, boleto, credit card, and subscriptions. Your agent manages customers, creates recurring charges, and tracks payment status.

Open

Pagar.me

@codespar/mcp-pagar-me · 22 tools

Payment gateway with card, Pix, and boleto. Receivables anticipation and risk management built for Brazilian marketplaces.

Open

Start in seconds.

On the CodeSpar runtime, the credential you connect stays encrypted for your organization and the runtime adds it to each call. You just call the tool.

Get started · free View docs

Start in seconds demo

Create an account and copy a test key.

Add the hosted endpoint to your client with the config above.

Connect PagBrasil in your project and ask your agent for the first call.