Mcp Stone

io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026

MCP server for Stone — open banking, payments, Pix, transfers

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Stone open banking that lets an assistant check balances, move money, charge cards and Pix, and manage receivables and terminals.

What you can do
Read account data: balance, transactions, statements, payments, receivables, terminals and webhooks, with filters and status checks. Create payments, bank transfers, outbound Pix payments, Pix charges, boletos and card charges. Tokenize cards for later charging. Refund settled transactions and cancel authorized ones. Request anticipation of future receivables and check anticipation limits. Register and list webhook endpoints for Stone events.
When to use it
Useful when an assistant should work with a Stone merchant account in Brazil: reviewing balances and statements, initiating or refunding payments, issuing Pix or boleto charges, or handling receivables and POS terminals. Best tried against the Stone sandbox before pointing it at live credentials.
Requirements
Runs locally via npx from the npm package @codespar/mcp-stone, so Node.js is needed. Requires Stone OAuth2 credentials: STONE_CLIENT_ID and STONE_CLIENT_SECRET, obtained by registering as a developer and creating an application. Optional STONE_BASE_URL and STONE_AUTH_URL override the API and token endpoints for sandbox use. Network access to Stone APIs.
Before you install
The credentials grant access to a real financial account and can move money: transfers, Pix payments, card charges, refunds, cancellations and anticipations all execute against the Stone API. Keep secrets in environment variables and prefer sandbox credentials while testing. Webhook registration changes account configuration. The README notes that versions up to 0.2.2 used a non-existent token host, so every tool failed at authentication.

Installation

In SourceWeft

  1. Open Mcp Stone 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-stone

MCP server for Stone — acquiring (card / Pix / boleto), anticipations, receivables, terminals, and open banking

[npm] [License: MIT]

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json
{  "mcpServers": {    "stone": {      "command": "npx",      "args": ["-y", "@codespar/mcp-stone"],      "env": {        "STONE_CLIENT_ID": "your-client-id",        "STONE_CLIENT_SECRET": "your-client-secret"      }    }  }}

Claude Code

bash
claude mcp add stone -- npx @codespar/mcp-stone

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

json
{  "servers": {    "stone": {      "command": "npx",      "args": ["-y", "@codespar/mcp-stone"],      "env": {        "STONE_CLIENT_ID": "your-client-id",        "STONE_CLIENT_SECRET": "your-client-secret"      }    }  }}

Tools (21)

ToolPurpose
get_balanceGet account balance
list_transactionsList account transactions
get_statementGet account statement for a period
create_paymentCreate a payment via Stone
get_paymentGet payment details by ID
list_paymentsList payments with optional filters
create_transferCreate a bank transfer (internal or external)
create_pix_paymentCreate a Pix payment (outbound) via Stone
create_pix_chargeCreate a Pix charge (QR Code / cob) to receive a payment
create_boletoCreate a boleto bancário for charging a customer
create_card_chargeCharge a credit or debit card (Stone acquiring)
tokenize_cardTokenize a card to PCI-safe token for later charging
refund_transactionRefund a settled transaction (full or partial)
cancel_transactionCancel an authorized (not-yet-captured) transaction
create_anticipationAnticipate future receivables (Stone's flagship 'antecipação')
get_anticipation_limitsGet current anticipation limits (max / min / available) for a merchant
list_receivablesSearch receivables (future credits from card transactions)
list_terminalsList physical Stone / TON terminals for a merchant
get_terminal_statusGet current status of a specific POS terminal (online / offline / last seen)
register_webhookRegister a webhook endpoint for Stone events
list_webhooksList registered webhook endpoints

Authentication

Stone uses OAuth2 client credentials for authentication. The server automatically manages token refresh.

Sandbox / Testing

Stone provides a sandbox via the developer portal.

Get your credentials

  1. Go to Stone Open Bank Documentation
  2. Register as a developer
  3. Create an application to get OAuth2 credentials
  4. Set the environment variables

Environment Variables

VariableRequiredDescription
STONE_CLIENT_IDYesOAuth2 client ID
STONE_CLIENT_SECRETYesOAuth2 client secret
STONE_BASE_URLNoOverride base URL (default https://api.openbank.stone.com.br/api/v1; sandbox https://sandbox-api.openbank.stone.com.br/api/v1)
STONE_AUTH_URLNoOverride the OAuth2 token URL (default https://accounts.openbank.stone.com.br/auth/realms/stone_bank/protocol/openid-connect/token; sandbox https://sandbox-accounts.openbank.stone.com.br/auth/realms/stone_bank/protocol/openid-connect/token). Up to 0.2.2 the token call went to login.openbank.stone.com.br, which does not exist, so every tool failed at authentication.

Roadmap

v0.3 (planned)

  • list_pix_keys — List registered Pix keys for a merchant
  • create_recipient — Marketplace / split recipients
  • create_transfer_batch — Batch transfer processing
  • get_boleto — Fetch boleto details
  • create_scheduled_payment — Schedule future-dated payments
  • list_payouts — List anticipation / settlement payouts

Want to contribute? Open a PR or request a tool.

Links

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/stone/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.2LatestSep 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