Adyen MCP server: connect AI agents to Adyen from the EU

Adyen N.V. is an Amsterdam-based payments platform used by large retailers, marketplaces and travel companies for online, in-app and in-store payments. Its MCP server, @adyen/mcp, is published by Adyen on GitHub under the MIT licence and documented on docs.adyen.com.

The server is in alpha and runs locally over stdio with npx. It covers Checkout sessions, payment links and modifications, and Management API areas for accounts, terminals, webhooks, payment methods and users. Recent versions add read-only, idempotent and destructive hints to each tool.

A customer service agent can look up a payment session, then prepare a refund for a returned order with the right PSP reference, waiting for a person to confirm. A sales team can create a payment link for a B2B order and check later whether it was paid.

Operations teams use it for the in-store estate: which terminals sit in which store, which settings apply, and scheduling actions such as app installs. Developers can list and test webhooks while debugging an integration, without opening the Customer Area for every check.

Adyen recommends creating a new webservice user for the MCP server, with only the roles the tools you plan to use require, and generating an API key for it. On inference.eu, add the Adyen connector to an agent and paste that key; it is stored encrypted in the EU.

Choose the TEST environment first. For LIVE, you also provide your live URL prefix from the Customer Area. Use the --tools option to expose only the tools a workflow needs, for example webhook tools for a developer agent.

The server calls Adyen's APIs directly, so payment and terminal data goes to and from Adyen, a Dutch company, exactly as with your existing integration. Adyen is the processor of record for these payments either way.

On inference.eu the model that reads payment details runs in EU data centres, and your API key is stored encrypted in the EU. Payment sessions and refunds can include shopper names, emails and partial card data, so keep this connector to the agents and people who handle payments today.

Refunds, cancellations, payment links and terminal changes have real effects, and the server is still alpha. Use a webservice user with narrow roles, start in the test environment, and enable only the tools you need.

On inference.eu, require a person to approve every tool marked as destructive, such as refunds, cancels, terminal reassignments and settings updates. Read tools such as listing webhooks or payment methods can run on their own. Keep the Adyen Customer Area as the place where people review the final state.