Mcp Picpay

io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026

MCP server for PicPay Business — BR digital wallet (60M+ users): checkout, Pix QR, subscriptions

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

A local MCP server for PicPay Business that lets an assistant create and manage Brazilian digital-wallet payments, Pix QR codes, payment links, subscriptions, B

What you can do
Create and manage checkout payments: create a payment, check status by reference, cancel, refund (optionally partial), and list merchant transactions in a date range. Generate Pix-style QR codes (static or dynamic with fixed amount and expiry) and shareable payment links. Manage subscription plans: create, list, update and delete plans, and enroll, retrieve or cancel subscriptions. Move money out: create Business-to-Person transfers, check transfer status, and submit batches of transfers. Check the merchant wallet balance in BRL and validate incoming webhook callbacks against the seller token.
When to use it
Useful when an assistant should operate a PicPay Business merchant account: taking payments, issuing Pix QR codes or payment links, running subscriptions, paying out to PicPay users, or reconciling transactions and balance. Best suited to developers integrating PicPay checkout into an agent workflow rather than casual end-user use.
Requirements
Runs locally over stdio via the npm package @codespar/mcp-picpay (Node.js required); an optional HTTP mode exists for server-to-server testing. Requires a PicPay merchant integration token in PICPAY_TOKEN and a seller token in PICPAY_SELLER_TOKEN. PICPAY_BASE_URL is optional and defaults to the public ecommerce API. Network access to PicPay is needed.
Before you install
Handles real money: transfers, batch payments, refunds, cancellations and plan deletion move or change funds and cannot be undone casually. The two tokens are merchant credentials sent as request headers; keep them out of logs and shared configs. Webhook payloads should be validated with the seller token before being trusted. The package is an alpha release, and the subscription endpoints' field-level schemas are not yet confirmed against the live API.

Installation

In SourceWeft

  1. Open Mcp Picpay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-picpay

MCP server for PicPay Business — Brazilian digital wallet with 60M+ users.

PicPay's Checkout API lets merchants create a payment intent that the buyer completes inside the PicPay app, returning a redirect URL plus a Pix-style QR code. The Recurrency API adds subscription plans on top.

Tools (20)

ToolPurpose
create_paymentCreate a PicPay checkout payment.
get_payment_statusGet the status of a payment by referenceId.
cancel_paymentCancel a PicPay order.
create_planCreate a subscription plan (Recurrency API).
list_plansList all subscription plans registered for this merchant.
update_planUpdate an existing subscription plan.
delete_planDelete a subscription plan.
create_subscriptionEnroll a buyer in a subscription plan.
get_subscriptionRetrieve a subscription by id.
cancel_subscriptionCancel an active subscription.
validate_notificationVerify that an incoming webhook callback came from PicPay by comparing the x-seller-token header against PI...
refund_paymentRefund a paid PicPay order, optionally partially.
create_b2p_transferCreate a Business-to-Person (B2P) transfer: push funds from the merchant wallet to a PicPay user identified...
get_b2p_transferGet the status of a B2P transfer by referenceId.
create_batch_paymentSubmit a batch of B2P transfers in a single request.
list_transactionsList merchant transactions (payments and transfers) within a date range.
get_wallet_balanceRetrieve the merchant's current PicPay wallet balance (available and blocked amounts in BRL).
generate_static_qrcodeGenerate a static PicPay Pay QR code for in-store / reusable use.
generate_dynamic_qrcodeGenerate a dynamic PicPay Pay QR code with a fixed amount and optional expiration.
create_payment_linkCreate a shareable PicPay payment link.

Install

bash
npm install @codespar/mcp-picpay@alpha

Environment

bash
PICPAY_TOKEN="..."          # Merchant integration token (x-picpay-token header)PICPAY_SELLER_TOKEN="..."   # Seller token used to validate webhook callbacksPICPAY_BASE_URL="..."       # Optional. Defaults to https://appws.picpay.com/ecommerce/public

Authentication

Every request sends:

Content-Type: application/jsonx-picpay-token: <PICPAY_TOKEN>

PicPay webhook callbacks carry x-seller-token: <PICPAY_SELLER_TOKEN>. Use the validate_notification tool (or compare the header yourself) before trusting a payload, then fetch the authoritative status with get_payment_status.

Run

bash
# stdio (default — for Claude Desktop, Cursor, etc)npx @codespar/mcp-picpay
# HTTP (for server-to-server testing)MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-picpay

Status

0.1.0-alpha.1. Core checkout endpoints (/payments, /payments/{ref}/status, /payments/{ref}/cancellations) are verified against PicPay's public docs. Recurrency (plans + subscriptions) endpoints come from the documented path shape but field-level schemas (frequency enum values, subscription response) should be confirmed against the live API before production use.

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/payments/picpay/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0-alpha.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts