Airwallex MCP Server – Payments Integration Tools
Airwallex's official Developer MCP and Docs MCP servers help AI coding agents build Airwallex integrations. Use Developer MCP for sandbox documentation and test tools, and Docs MCP for unauthenticated read-only access to Airwallex product and API documentation.
Overview
Airwallex provides official MCP connectors for AI agents that help developers build and test integrations with the Airwallex financial platform. The Developer MCP server is a sandbox-focused MCP server for coding agents, while Docs MCP is a documentation-only server for agents that only need Airwallex knowledge and no API access.
What the MCP server enables
Airwallex documents three connector paths: the Airwallex CLI for broad terminal automation, Developer MCP for sandbox coding workflows, and Docs MCP for read-only documentation access. This YAML describes the official MCP servers.
Developer MCP exposes Airwallex documentation tools, sandbox simulation tools, and selected sandbox endpoints. It helps coding agents retrieve current Airwallex documentation, inspect API surfaces, generate integration code, and create or test sandbox resources while building Airwallex integrations. Local Developer MCP can provide fuller sandbox tool access, including billing tools, when configured with sandbox credentials.
Docs MCP exposes the same documentation search tools as Developer MCP but does not require authentication. It is intended for assistants that only need to search Airwallex product and API documentation.
When to use it
Use Airwallex Developer MCP when a coding agent is building or testing Airwallex integrations in sandbox, such as creating a test payment link, implementing checkout, building billing or subscription workflows, testing webhooks, or exploring Airwallex API parameters. Use Docs MCP when the agent only needs reliable Airwallex documentation and API guidance without calling sandbox APIs.
For production reads and writes, Airwallex currently directs users to the Airwallex CLI. Airwallex's production MCP for non-terminal environments is documented as coming soon.
Connection and authentication
The Developer MCP remote endpoint is:
https://mcp-demo.airwallex.com/developer
Remote Developer MCP uses OAuth against an Airwallex sandbox account in supported clients. The local Developer MCP server runs with:
npx -y @airwallex/developer-mcp@latest
Local mode can use sandbox credentials in AIRWALLEX_SANDBOX_CLIENT_ID, AIRWALLEX_SANDBOX_API_KEY, and AIRWALLEX_SANDBOX_ACCOUNT_ID. DISABLE_TELEMETRY=true disables telemetry.
The Docs MCP endpoint is:
https://mcp-demo.airwallex.com/docs
Docs MCP requires no authentication.
Key considerations
Developer MCP direct API testing tools run in sandbox only. Airwallex documents that production operations require the CLI or the future production Airwallex MCP. Generated code and recommendations must be reviewed, validated, and tested before production use. Some Airwallex resources, such as cards and issuing, may require additional account permissions. Local server telemetry is enabled by default and collects basic anonymous usage data unless disabled; Airwallex states tool parameters and responses are not logged for local telemetry. Keep sandbox API credentials out of source control and never put real credentials directly into MCP configuration files.
Supported Transports
streamable_http
URL: https://mcp-demo.airwallex.com/developer
streamable_http
URL: https://mcp-demo.airwallex.com/docs
stdio
Command: npx
Args:
-y@airwallex/developer-mcp@latest
Frequently Asked Questions
- When should an AI agent use the Airwallex MCP server?
- Use Developer MCP when a coding agent is building or testing Airwallex integrations in sandbox, such as payment links, checkout, billing, subscriptions, API requests, or webhook flows. Use Docs MCP when the agent only needs Airwallex documentation and API guidance.
- What does the Airwallex MCP server add to an AI agent's capabilities?
- It gives the agent access to current Airwallex documentation, API reference knowledge, integration guidance, and sandbox testing tools so it can generate better code and reduce hallucinated API specs.
- What can an AI agent access or manage through Airwallex MCP?
- Developer MCP exposes documentation tools, sandbox simulation tools, and selected sandbox endpoints. Local Developer MCP can provide fuller sandbox tool access, including billing tools, when configured with sandbox credentials. Docs MCP exposes documentation search tools only.
- How is authentication configured for the Airwallex MCP server?
- Remote Developer MCP uses OAuth with an Airwallex sandbox account in supported clients. Local Developer MCP uses sandbox credentials supplied as AIRWALLEX_SANDBOX_CLIENT_ID, AIRWALLEX_SANDBOX_API_KEY, and AIRWALLEX_SANDBOX_ACCOUNT_ID. Docs MCP requires no authentication.
- Which transport should be used for the Airwallex MCP server?
- Use the remote HTTP Developer MCP endpoint at https://mcp-demo.airwallex.com/developer for OAuth-based sandbox tools, the remote HTTP Docs MCP endpoint at https://mcp-demo.airwallex.com/docs for unauthenticated documentation search, or the local stdio package npx -y @airwallex/developer-mcp@latest when fuller sandbox tool access is needed.