Airwallex Developer
Search Airwallex documentation and exercise a sandbox account from an AI agent. Anthropic lists 12 tools; Airwallex publishes no tool list. Sandbox only — the connector cannot reach a production account, and its writes move no real money.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Airwallex Developer via MCP
https://mcp-demo.airwallex.com/developerWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Airwallex Developer Tools & Capabilities (12)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Sandbox only. Airwallex lists this as a limitation in its own documentation and directs production reads and writes to the Airwallex CLI or the AgentOS MCP server instead. If you want an agent to act on a real account, this connector is the wrong one by design.
- Airwallex publishes no tool list for this server. The 12 names come from Anthropic's directory. We could not diff them against a vendor enumeration because none exists, in the docs or in the public marketplace repository.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.
- The directory endpoint disagrees with every vendor source. Anthropic lists
mcp-demo.airwallex.com; Airwallex documentsmcp.sandbox.airwallex.com. Both were live on 2026-08-22 with identical OAuth metadata, but a-demohostname is not the one the vendor tells you to configure. - Scopes exist for capability the tool list does not show. Twenty-one write scopes are advertised, covering issuing, disputes, linked accounts and billing, against four write tools. We could not determine which subset is actually requested at consent.
- Consent breaks when people change roles. Airwallex binds OAuth consent to the granting user and invalidates it the moment that user loses Owner, Admin or Finance Admin, or leaves. Token refresh then fails with
invalid_grantand an administrator must reconnect. - Sandbox rate limits are tight. 20 requests per second globally, 10 per endpoint, 10 concurrent — a fifth of production on the global figure. HTTP 429 on exceeding any of them.
- Sandbox data is not durable. Airwallex deletes files generated or uploaded in the sandbox after 90 days.
- Quality is model-dependent, by Airwallex's own admission. Its documentation states quality varies by model, that no model is perfect, and that hallucination is reduced rather than eliminated. It asks that generated code be reviewed and tested before production use.
- Connected Account APIs are excluded from sandbox. Airwallex states the sandbox covers all products except Connected Account APIs, which require contacting its sales team.
Frequently asked questions
No. Airwallex documents this connector as sandbox only, stating it runs against the sandbox and never touches your production account. You authorize it with sandbox credentials, so a create_transfer call moves test balances inside a simulated environment. Airwallex routes production reads and writes to a separate connector at a different endpoint.
No, and the distinction is the whole point of the listing. Two of the 12 tools search docs and best practices. The other ten create transfers, payment links and deposits, list beneficiaries, global accounts and balances, and simulate transfer results. Airwallex calls the documentation-only variant Docs MCP and ships it as a separate, unauthenticated server.
Forty-eight named scopes, split by an explicit read and write prefix. The server's RFC 9728 descriptor advertised 27 scopes beginning r: and 21 beginning w: on 2026-08-22, covering balances, transfers, payment links, issuing cards, deposits and billing. The boundary is real and unusually granular, though consent is granted per connection rather than per tool call.
Airwallex documents https://mcp.sandbox.airwallex.com/developer, and every first-party source agrees on it. Anthropic's directory publishes https://mcp-demo.airwallex.com/developer instead. Both hosts answered on 2026-08-22 and served an identical scope list, so they appear to be one deployment behind two names. Prefer the vendor-documented hostname.
Only an Owner, Admin or Finance Admin. Airwallex documents these as the roles that can grant OAuth consent, and it binds each consent to the individual who granted it. If that person loses the role or leaves, the consent becomes invalid immediately and token refresh fails with invalid_grant, so a current administrator must reconnect.
Because the OAuth flow expired before you finished it. Airwallex documents that the tokens behind the remote endpoint expire quickly and asks you to complete authorization within a few minutes of starting it. Re-run the one-click install or OAuth flow, and confirm you are authorizing with the sandbox account you intended to use.
Twelve, according to Anthropic's directory. Airwallex publishes no tool list anywhere we could find — its connector guide shows only a two-row table marking documentation and sandbox tools present or absent. So there is no vendor enumeration to check the twelve against, which is a weaker position than a clean diff.
Sandbox limits are roughly a fifth of production. Airwallex documents 20 requests per second globally in sandbox against 100 in production, 10 per second per endpoint against 20, and 10 concurrent requests against 50. Exceeding any of them returns HTTP 429. Sandbox files are also deleted automatically after 90 days.
Sources
- Airwallex developer connectors guide (retrieved 2026-08-22). The directory's
documentationURL,.../ai/developer-mcp, meta-refreshes to this page — a rename, not a dead link. · retrieved 2026-08-22 - Airwallex AgentOS documentation (retrieved 2026-08-22) · retrieved 2026-08-22
- Airwallex AI tooling best practices and troubleshooting (retrieved 2026-08-22) · retrieved 2026-08-22
- Airwallex sandbox environment overview (retrieved 2026-08-22) · retrieved 2026-08-22
- Airwallex API rate limits (retrieved 2026-08-22) · retrieved 2026-08-22
- Airwallex OAuth permissions and user roles (retrieved 2026-08-22) · retrieved 2026-08-22
- Airwallex documentation index,
llms.txt(retrieved 2026-08-22). Every page above was read as Markdown via the.mdsuffix this index publishes. · retrieved 2026-08-22 - Airwallex marketplace repository, plugin MCP configuration (retrieved 2026-08-22) · retrieved 2026-08-22
- Live auth posture check: anonymous
initializereturned HTTP 401 with awww-authenticatechallenge naming the resource metadata document, and RFC 9728 metadata was read athttps://mcp-demo.airwallex.com/.well-known/oauth-protected-resource/developer/and at the vendor hosthttps://mcp.sandbox.airwallex.com/.well-known/oauth-protected-resource/developer/(2026-08-22). Control probes at sibling well-known paths returned matching 404 bodies, so the descriptor is genuine rather than a catch-all. · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Airwallex
robots.txtallows/docs/and declares noContent-Signalrestriction (retrieved 2026-08-22) · retrieved 2026-08-22 - Airwallex developer support — <mailto:developer.support@airwallex.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Airwallex Developer
- Tools
- 12
- Domain
- mcp-demo.airwallex.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.