adyen

This MCP server exposes Adyen's MCP capabilities to LLMs through a set of API tools. It includes CheckoutAPI endpoints for creating and retrieving payment sessions, obtaining available payment methods, and working with payment links; Checkout API modifications for cancelling or refunding payments; Management API endpoints for accounts, terminals, and webhooks; and various terminal and settings related actions. You can invoke these tools from your LLM by calling the corresponding functions (e.g., create a session, fetch payment methods, or manage a payment link) via the MCP server. The provided example demonstrates running the MCP server with npx and supplying your Adyen API key and environment. When using the live environment, you should also provide your live URL prefix as needed.

Typical usage involves starting the MCP server and then issuing function calls from your client or LLM to these tools. For example, you can create a payment session, query available payment methods, generate a payment link, or cancel/refund a payment. Advanced operations cover terminal management (listing terminals, reassigning terminals, and updating terminal settings) and webhook management.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to the Adyen MCP package via npm registry

Installation steps:

1. Install Node.js from https://nodejs.org/ (if not already installed)

2. Ensure npm is up to date:

   npm install -g npm

3. Run the MCP server using npx (no global install required):

   npx -y @adyen/mcp --adyenApiKey=YOUR_ADYEN_API_KEY --env=TEST

4. If you are planning to run this in a development environment with Codespaces or a container, you can use the provided npm package name to install dependencies and run locally:

   npm install @adyen/mcp node path/to/server.js // if the package exposes a start script

Prerequisites note: Replace YOUR_ADYEN_API_KEY with a valid webservice user API key that has the required roles for the tools you intend to use (as documented by Adyen). For live environments, include the live prefix as required by Adyen.

Notes and tips:

• Use a dedicated Adyen webservice user and API key with only the necessary roles for the tools you plan to use to follow least-privilege best practices.
• If you switch to the LIVE environment, ensure you pass --env=LIVE and provide the livePrefix (e.g., --livePrefix=https://live-urls.example.com).
• The MCP server supports a variety of tools ranging from Checkout API sessions and payment links to management and terminal actions. Refer to the Adyen MCP documentation for the exact API shapes and required parameters.
• In the VSCode example, an explicit env mapping shows how to pass sensitive values. Do not commit real API keys in code or configuration files.
• If you encounter permissions or 403 errors, verify the API key has the appropriate roles (Accounts Read, Payment Methods Read, Terminal actions, Webhooks read, etc.) as listed in the README.