@airwallex/developer-mcp

What changed

Changed between 4 September 2026 and 5 October 2026 (first seen 2026-10-05 14:34 UTC)

1 description rewritten.

--- pinned/search_public_docs
+++ observed/search_public_docs
  {
    "annotations": {
+     "destructiveHint": false,
+     "idempotentHint": true,
      "openWorldHint": true,
      "readOnlyHint": true,
      "title": "Search Airwallex Product, API & SDK documentation"
-   "description": "Retrieve relevant sections from the official Airwallex documentation matching the user's question.\n  \nUSAGE STRATEGY:\n  DO: Prefer to start with a broad search without specifying any source and then narrow down the search with a specific source when needed\n  DO: For relevant API endpoints or SDK methods in the sections returned, invoke this tool again with the specific source to get more detailed information\n  DO: For API endpoints referenced, always remember to explicitly check how to perform API authentication\n  DO: For SDK methods referenced, always remember to explicitly check how to initialize the SDK\n\nPRIVACY & SECURITY REQUIREMENTS:\n• DON'T: Include PII (Personally Identifiable Information) in questions\n• DON'T: Include account IDs, user IDs, email addresses, or customer data\n• DON'T: Include API keys, tokens, or credentials\n• DON'T: Include transaction IDs, payment references, or financial data\n• DO: Use generic examples like 'how to process payments' instead of specific account details\n• DO: Focus on technical concepts, API endpoints, and implementation patterns\n• DO: API version information is permitted as an exception (e.g., '2023-09-30')",
+   "description": "Retrieve relevant sections from the official Airwallex documentation matching the user's question.\n\nNOTE: The required parameters is QUESTION instead of query.\n\nUSAGE STRATEGY:\n  DO: For API endpoints referenced, always remember to explicitly check how to perform API authentication\n  DO: For SDK methods referenced, always remember to explicitly check how to initialize the SDK\n\nQUERY REWRITE:\n  DO: Rewrite the user's text into one natural, concise, straightforward English question before calling, with a clear intent (what is, how to, or why)\n  DO: Keep the substance of the user's query; do not drop topics, identifiers, or constraints they mentioned\n  DON'T: Split by default — use one call unless the query has clearly different topics that one question cannot cover. Do not split related keywords on the same topic, tightly coupled parts, or near-duplicate phrasings of the same intent\n  DO: Rewrite unstructured keyword pastes that are not real questions (no \"?\", does not start with How/What/...) into natural English questions. When keywords span different topics, rewrite into one question per topic and use multiple calls.\n    Example: \"Airwallex.js getting started, installation, hosted payment page, drop-in element, embedded elements, card element list of all payment elements\" → \"How do I get started with and install Airwallex.js for a hosted payment page or drop-in element?\" and \"What are all the available embedded payment elements in Airwallex.js, including the card element?\".\n  DO: Use separate calls for multi-part asks (two \"?\", or \"... and ...\" linking separate questions) — one question per ask.\n    Example: \"Does the Create PaymentConsent API support a metadata field? Can metadata be set on a payment consent created via the drop-in element in recurring mode?\" → two calls\n\nLANGUAGE REQUIREMENT:\n• DO: Always submit the question parameter in English\n• DO: If the user asks in another language, translate their question to English before calling this tool\n• DON'T: Pass non-English text in the question parameter\n\nPRIVACY & SECURITY REQUIREMENTS:\n• DON'T: Include PII (Personally Identifiable Information) in questions\n• DON'T: Include account IDs, user IDs, email addresses, or customer data\n• DON'T: Include API keys, tokens, or credentials\n• DON'T: Include transaction IDs, payment references, or financial data\n• DO: Use generic examples like 'how to process payments' instead of specific account details\n• DO: Focus on technical concepts, API endpoints, and implementation patterns\n• DO: API version information is permitted as an exception (e.g., '2023-09-30')",
    "inputSchema": {
      "$schema": "http://json-schema.org/draft-07/schema#",
      "additionalProperties": false,
-         "description": "The question to search the documentation with.",
+         "description": "The question to search the documentation with. Must be written in English; translate from the user's language before calling if needed.",
          "minLength": 1,
          "type": "string"
-       },
-       "source": {
-         "description": "Documentation source to search. OMIT this parameter to search all sources. PREFER to start with a broad search and then narrow down the search with a specific source if needed. Set the source to `product-docs` for information related to integration or migration guides, general product enquiries & detailed API response error code descriptions and reasons. Set the source to `api-docs` for information related to specific API endpoints and for general API-related information related to versioning, authentication, rate limits, etc. Set the source to `js-sdk-docs` for specific information related to Airwallex.js or the Components SDK. For the legacy JS libraries, use `product-docs`, `ios-sdk-docs` for specific information related to the Payments iOS SDK, `android-sdk-docs` for specific information related to the Payments Android SDK.",
-         "enum": [
-           "product-docs",
-           "api-docs",
-           "js-sdk-docs",
-           "ios-sdk-docs",
-           "android-sdk-docs"
-         ],
-         "type": "string"
        }
      },
      "required": [

Current tools

Watch this server yourself

If you run this server, put the proxy in front of it. It pins these exact fingerprints on first connect and stops the session if they move.

npx -y mcp-pin@0.2.3 -- <your @airwallex/developer-mcp command>

Or subscribe to this page's RSS feed to be told when it changes.

Badge

The badge states one fact about time and nothing else. It never claims a server is safe.

[![mcp-pin](https://mcp-pin.gautamkhosla.com/badge/86d1461c373e5f17.svg)](https://mcp-pin.gautamkhosla.com/servers/86d1461c373e5f17.html)