NAKPIX MCP Server
OfficialEnables AI agents to validate and parse PIX payment data, get quotes, pay PIX via natural-language commands, retrieve receipts and payment status, and schedule future or recurring PIX payments.
Supports creating local Polygon wallets, checking USDT/POL balances and on-chain deposits, and paying PIX with USDT on Polygon.
Supports creating local Solana wallets, checking USDT/SOL balances and on-chain deposits, and paying PIX with USDT on Solana.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NAKPIX MCP Serverpay this PIX bill for R$ 120 to João using my USDT balance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NAKPIX MCP Server
Official NAKPIX integration for AI agents (OpenClaw, Hermes, Claude, OpenCode and other MCP-compatible clients). Pay PIX with crypto (USDT on Polygon/Solana) — no conventional account, no mandatory KYC.
The MCP reuses NAKPIX's existing financial backend: order creation, quoting, coupon validation and PIX execution. It does not reimplement payment processing.
⚠️ The backend remains private. This repository contains no seeds, private keys, credentials or production data. See SECURITY.md.
What agents can do
Create a Polygon or Solana wallet locally (encrypted).
Get the public address and a secure backup (recovery words via CLI only).
Check USDT/POL/SOL balances and deposits on-chain.
Maintain a persistent PIX contact agenda.
Set a permanent default discount coupon.
Pay PIX with natural-language commands.
Pay bills received as audio/image/QR/text/PDF.
Schedule future and recurring payments (confirmed once, at creation).
Receive real receipts and real failure reasons.
Get alerts when an operation is unresolved for 15+ minutes.
Related MCP server: remit.md MCP Server
Architecture
agent (LLM)
│ MCP (stdio)
▼
nakpix-mcp server ──► nakpix-wallet-agent (LOCAL, keys stay here)
│ └─ ~/.nakpix/wallets/*.json (encrypted)
├──► backend HTTP (nakpix.xyz relays — existing processing)
├──► blockchain (balance/deposit read-only)
├──► scheduler (persistent, background process)
└──► incidents (15-min unresolved monitor + agent notification)The wallet-agent is the only component that touches secret material. The MCP server never sees seeds, mnemonics or private keys — wallet tools return public data only.
Install
git clone https://github.com/nakpix/nakpix-mcp
cd nakpix-mcp
python -m venv .venv && source .venv/bin/activate
pip install -e .Configure
cp .env.example .env # fill NAKPIX_BACKEND_URL, RPCsLocal data lives in ~/.nakpix/ (wallets encrypted with Argon2id + AES-256-GCM,
contacts, settings, SQLite DB, logs). Wallets are mode 0600, dirs 0700.
Run
The MCP server runs over stdio and is launched by your agent client:
nakpix-mcpThe background services run independently (needed for scheduled/recurring payments and the 15-minute incident monitor to work while no chat is open):
nakpix-scheduler # executes due schedules (idempotent)
nakpix-incidents # opens incidents + enqueues notification for the agent to emailOr with Docker:
docker compose up -d # scheduler + incidentsWallet CLI (secure interface)
nakpix-wallet-agent status
nakpix-wallet-agent create polygon
nakpix-wallet-agent reveal polygon # shows recovery words (terminal only)
nakpix-wallet-agent mark-backed-up polygonRecovery words are never exposed through MCP/chat/logs — only through the local CLI.
Tools
nakpix_wallet_status, nakpix_create_wallet, nakpix_import_wallet,
nakpix_get_wallet_address, nakpix_get_balances, nakpix_get_deposits,
nakpix_get_supported_networks, nakpix_get_wallet_backup_status,
nakpix_add_contact (+ list/get/find/update/delete), nakpix_set_default_coupon
(+ get/remove/validate), nakpix_validate_pix, nakpix_parse_pix,
nakpix_get_quote, nakpix_pay_pix, nakpix_get_payment_status,
nakpix_get_receipt, nakpix_get_payment_history,
nakpix_get_transaction_details, nakpix_schedule_payment,
nakpix_schedule_recurring_payment (+ list/get/update/cancel/pause/resume/
history), nakpix_get_payment_confirmation (+ set), nakpix_get_notifications.
Agent Skill
The companion agent skill lives at nakpix-agent-skill and teaches the agent the full flow (first-use wallet creation, confirmation, scheduling, document reading, incident handling).
License
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Accept Pix in Brazil and settle in USDT/USDC; pay Pix with crypto; verify a Pix with no API key.
Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP.
Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.
Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to interact with cryptocurrency ecosystems through wallet management, trading operations (swaps, DCA, limit orders), staking, and multi-chain support starting with Solana.37GPL 3.0
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.2 npmMIT
- AlicenseBqualityBmaintenanceProvides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.40288 npm3MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.3660 npm4Apache 2.0