Airwallex Docs MCP gives AI agents read-only access to Airwallex documentation and API references, enabling agents to search and retrieve accurate integration guidance without authentication.
Cursor is an AI-first code editor. It loads MCP servers from its settings and lets its agent call their tools as part of a task.
This guide connects Airwallex Docs MCP to Cursor through MewCP, so Cursor can use Airwallex Docs MCP's 2 tools, like read_integration_best_practices and search_public_docs.
Airwallex Docs MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Manage repositories, pull requests, issues, branches and development workflows on GitHub. Automate software delivery and collaborate across engineering projects.
Connect to external APIs, webhooks and internet services through standard HTTP requests. Build integrations with virtually any platform that exposes a web-based interface.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
HotAPI provides a unified API for AI-powered image, video, and audio generation, image editing, and conversational AI. Developers can access multiple models through a single API key, track asynchronous generation tasks, and retrieve results with polling or webhooks.
Other clients
Airwallex Docs MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Airwallex Docs MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
CODE GENERATION AND PAYMENT DISPUTE FLOW ONLY: This tool MUST be called before any other Airwallex tools, but ONLY when the user intent is to generate code or trigger payment dispute flow. For documentation searches, general questions, or non-code-related tasks, skip this tool and proceed directly with the appropriate tools for the task at hand. SINGLE USE PER CONVERSATION: You MUST call this tool only ONCE per conversation. The best practices content is static and doesn't need to be re-read multiple times. This tool reads the Airwallex integration best practices documentation that contains essential guidelines for API usage, payment handling, SDK implementation, and common pitfalls to avoid.
Retrieve relevant sections from the official Airwallex documentation matching the user's question. NOTE: The required parameters is QUESTION instead of query. USAGE STRATEGY: DO: For API endpoints referenced, always remember to explicitly check how to perform API authentication DO: For SDK methods referenced, always remember to explicitly check how to initialize the SDK QUERY REWRITE: 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) DO: Keep the substance of the user's query; do not drop topics, identifiers, or constraints they mentioned 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 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. 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?". DO: Use separate calls for multi-part asks (two "?", or "... and ..." linking separate questions) — one question per ask. 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 LANGUAGE REQUIREMENT: • DO: Always submit the question parameter in English • DO: If the user asks in another language, translate their question to English before calling this tool • DON'T: Pass non-English text in the question parameter PRIVACY & SECURITY REQUIREMENTS: • DON'T: Include PII (Personally Identifiable Information) in questions • DON'T: Include account IDs, user IDs, email addresses, or customer data • DON'T: Include API keys, tokens, or credentials • DON'T: Include transaction IDs, payment references, or financial data • DO: Use generic examples like 'how to process payments' instead of specific account details • DO: Focus on technical concepts, API endpoints, and implementation patterns • DO: API version information is permitted as an exception (e.g., '2023-09-30')
