Mcp Ebanx
Wire EBANX cross-border payments, payouts, and FX into Claude Code or Cursor so your agent can quote rates and drive payouts without leaving the chat.
Overview
io.github.codespar/mcp-ebanx is a MCP server for the Build phase that connects coding agents to EBANX for cross-border payments, payouts, and exchange rates.
What is this MCP server?
- Stdio MCP transport (@codespar/mcp-ebanx v0.1.2) for agent-driven EBANX API calls
- Cross-border payments, merchant payouts, and exchange-rate lookups in one server
- Single required secret: EBANX_API_KEY configured as an environment variable
- Part of codespar mcp-dev-brasil payments package family on GitHub
- npm registry install path aligned with Model Context Protocol server.schema.json
- Server version 0.1.2
- 1 npm package (@codespar/mcp-ebanx) with stdio transport
- 1 required secret environment variable (EBANX_API_KEY)
Community signal: 252 GitHub stars.
What problem does it solve?
Agents guess at EBANX endpoints and payout fields unless you manually paste API docs every time you touch billing code.
Who is it for?
Indie builders with an EBANX account who want agent-assisted payment and FX integration in Node-friendly MCP hosts.
Skip if: Teams without EBANX credentials, pure domestic-only Stripe stacks, or anyone who needs a hosted checkout widget instead of API tooling.
What do I get? / Deliverables
After you register the server with EBANX_API_KEY set, your agent can invoke structured tools against your EBANX account while you implement checkout and payout automation.
- Registered stdio MCP server exposing EBANX payment and FX-oriented tools
- Agent-accessible calls aligned with your EBANX API credentials
- Repeatable integration setup documented in your local MCP config
Recommended MCP Servers
Journey fit
Payment provider wiring happens while you are building checkout, billing, and payout flows—not during early ideation. EBANX is an external payments API; the natural shelf is integrations where MCP servers connect agents to third-party money rails.
How it compares
EBANX MCP integration for agent tool calls, not a standalone payment SDK or no-code billing dashboard.
Common Questions / FAQ
Who is io.github.codespar/mcp-ebanx for?
Solo builders and small teams shipping paid products in LATAM who already use EBANX and want Claude Code or Cursor to help with payments and FX API work.
When should I use io.github.codespar/mcp-ebanx?
Use it during Build when you are wiring cross-border checkout, payouts, or rate lookups—not before you have merchant API keys and a clear billing design.
How do I add io.github.codespar/mcp-ebanx to my agent?
Install @codespar/mcp-ebanx from npm, export EBANX_API_KEY, configure stdio MCP in your host, and restart the agent so the EBANX tools load.