Adyen MCP: Documentation

Connection

npx -y @adyen/mcp --adyenApiKey=YOUR_KEY --env=TEST (stdio). For LIVE, add --livePrefix=YOUR_PREFIX (see Adyen's docs on the live URL prefix). The --tools=list_all_company_webhooks,... flag can start just a subset instead of every tool at once. You'll need an Adyen webservice user with roles scoped to the specific APIs (Checkout Webservice, Merchant PAL, section-specific Management API roles).

Tools

25+ tools across 10 areas:

• Checkout — Sessions: CreateSession and fetching a session's result, available payment methods.
• Checkout — Payment Links: create, check status, force-expire a link.
• Checkout — Modifications: cancel an authorized payment, RefundPayment.
• Management — Accounts: ListMerchantAccounts.
• Management — Terminals: list, reassign, Android apps and certificates, terminal actions and settings.
• Management — Webhooks: list, fetch, test a webhook.
• Management — Payment methods, Users, API Credentials, Allowed Origins — read-only reference operations.

Agent flow

"Create an €80 payment session for order #920", "refund payment psp_88213", "show me the store's terminal list", "test the webhook with this ID".

Important

An Adyen API key directly controls the seller's money (cancellations, refunds). Adyen recommends creating a dedicated webservice user with roles scoped strictly to the tools you need, and never using a live key for testing — start on the TEST environment.

Pricing

The MCP server is free, MIT licensed (the project is in Alpha, expect breaking changes); payment processing is billed at Adyen's regular rates.