
Mcp Airwallex
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Airwallex — cross-border collection + payouts, global accounts, FX, transfers
Overview
Airwallex MCP server that lets an assistant create and manage payment intents, refunds, customers, beneficiaries, transfers and FX conversions.
- What you can do
- Create, confirm, capture, cancel, retrieve and list payment intents, and issue or look up refunds
- Create, retrieve and update customers for saved payment methods and recurring charges
- Create, retrieve and list transfer beneficiaries with bank details
- Create, retrieve, cancel and list cross-border transfers to beneficiaries
- Execute FX conversions between wallet currencies and read wallet balances per currency
- When to use it
- Useful when an assistant should handle Airwallex cross-border collection and payouts: taking payments, refunding, managing customers and beneficiaries, sending transfers, or converting and checking balances, ideally against the demo environment first.
- Requirements
- Runs locally via npx from the npm package @codespar/mcp-airwallex (Node.js). Needs AIRWALLEX_CLIENT_ID and the secret AIRWALLEX_API_KEY, plus AIRWALLEX_ENV set to demo (default) or production. Network access to the Airwallex API; the server logs in to obtain a bearer token.
Installation
In SourceWeft
- Open Mcp Airwallex in the dashboard and add it to a workspace.
- 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-airwallex
MCP server for Airwallex — embedded finance for cross-border collection and payouts.
EBANX lets global platforms collect FROM LatAm and settle to USD. Airwallex is the inverse: LatAm sellers collect FROM abroad (USD, EUR, GBP) into global accounts, convert FX, and pay beneficiaries out across 150+ countries. Together the two servers bracket the cross-border flow both ways.
Tools (20)
Install
Environment
Base URLs:
demo→https://api-demo.airwallex.com/api/v1production→https://api.airwallex.com/api/v1
Authentication
Token flow. On first call the server POSTs to /authentication/login with headers x-client-id and x-api-key (no body). Airwallex returns { token, expires_at } (JWT, ~30 min lifetime). The server caches the token in memory and refreshes it 60 seconds before expiry. Every subsequent call sends Authorization: Bearer <token>.
Idempotency
Every create_* tool takes a required request_id parameter. Airwallex uses this as the idempotency key. The server never auto-generates it — agents must pass a stable UUID per logical operation so retries are safe.
Run
Positioning vs EBANX
Pair both for bidirectional cross-border coverage.
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/airwallex/README.md at commit d0a519a
Tools
0Version history
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