Mcp Stone
Connect your coding agent to Stone for open banking, Pix, payments, and transfers while you ship Brazil payment features.
Overview
io.github.codespar/mcp-stone is a MCP server for the Build phase that connects agents to Stone open banking, payments, Pix, and transfers.
What is this MCP server?
- Open banking, payments, Pix, and transfers per Stone MCP description
- @codespar/mcp-stone npm v0.1.2 with stdio transport
- STONE_CLIENT_SECRET required secret for API authentication
- Published from codespar/mcp-dev-brasil (packages/payments/stone)
- Pairs conceptually with mcp-stark-bank for multi-provider Brazil stacks
- Package version 0.1.2 (@codespar/mcp-stone)
- 4 capability areas in description: open banking, payments, Pix, transfers
- 1 required secret env var: STONE_CLIENT_SECRET
Community signal: 252 GitHub stars.
What problem does it solve?
Builders on Stone still copy API docs manually because agents lack a first-class MCP path to Pix and open-banking endpoints.
Who is it for?
Solo developers using Stone acquirer/banking APIs who want agent-assisted Pix, payment, and transfer implementation.
Skip if: Merchants not on Stone, global-only Stripe stacks, or teams that need accounting (Siigo) rather than payment acquiring.
What do I get? / Deliverables
With STONE_CLIENT_SECRET set, your agent can call Stone-backed MCP tools while you build and refine Brazil payment integrations.
- Configured Stone MCP stdio server in agent settings
- Agent tools for open banking, payments, Pix, and transfers
- Secret STONE_CLIENT_SECRET stored outside committed config
Recommended MCP Servers
Journey fit
Stone payment and open-banking hooks belong in the build phase when you wire checkout, payouts, or banking features into your product. Stone is an external payments API—MCP exposes it as agent tools under integrations, alongside other Brasil fintech connectors.
How it compares
Stone payments MCP integration, not Stark Bank’s banking API set—choose by your existing processor contract.
Common Questions / FAQ
Who is io.github.codespar/mcp-stone for?
Brazil-focused solo builders and tiny teams on Stone who want Cursor, Claude Code, or Codex to invoke payment and Pix APIs through MCP.
When should I use io.github.codespar/mcp-stone?
Use it during build when integrating open banking, card or Pix payments, or transfers that Stone already powers for your business.
How do I add io.github.codespar/mcp-stone to my agent?
Register @codespar/mcp-stone with stdio MCP, add STONE_CLIENT_SECRET as a required secret env var, and restart your agent client.