--- title: "Adyen MCP server · Connect AI agents to Adyen payments" description: "Connect inference.eu agents to Adyen's official MCP server. Create payment sessions and links, handle refunds and cancels, and manage terminals and webhooks." canonical: "https://inference.eu/connect/adyen/" language: "en" --- MCP servers · Banking and payments # Adyen MCP server: connect AI agents to Adyen from the EU Adyen publishes an official, open-source MCP server, currently in alpha, that exposes parts of its Checkout and Management APIs as tools. inference.eu agents use it with a dedicated Adyen API key, so payment and operations teams can create payment links, process refunds and inspect terminals and webhooks by asking in plain language. [Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools) 1. 01Authentication: API key 2. 02Official server 3. 03EU data centres ## What agents can do with it - 1 ### Checkout sessions and payment links Create a payment session and read its result, list the payment methods available for an amount and country, and create, check or expire payment links. - 2 ### Refunds and cancellations Refund a captured payment or cancel an authorised one by its PSP reference, through the Checkout API modifications endpoints. - 3 ### Merchant, terminal and webhook management List merchant accounts, users and payment method settings, list and reassign terminals or change terminal settings, and list, inspect and test webhooks at company or merchant level. ## What Adyen and its MCP server are 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. ## What agents can do with Adyen 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. ## Setup and authentication 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. ## Data protection and where the data goes 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. ## Approvals and safe use 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. ## Adyen Vendor Adyen N.V. Vendor based in Netherlands Category Banking and payments Authentication API key Transport Local (stdio) Server [Official server](https://github.com/Adyen/adyen-mcp) Documentation [docs.adyen.com](https://docs.adyen.com/development-resources/mcp-server/) ## Adyen: common questions The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly. Yes. Adyen publishes \`@adyen/mcp\` on GitHub and documents it on docs.adyen.com. As of November 2026 it is labelled alpha. It runs locally over stdio and authenticates with an Adyen API key for the test or live environment. Checkout API sessions, payment methods, payment links and modifications such as refunds and cancels, plus Management API endpoints for merchant accounts, terminals and Android apps, terminal settings and actions, webhooks, payment method settings and users. Yes. The server can refund a captured payment or cancel an authorised one using its PSP reference. Because these tools are destructive, we recommend requiring a person's approval on inference.eu before every call. A new one for a dedicated webservice user. Adyen recommends creating that user for the MCP server and giving it only the roles the chosen tools need, such as the Checkout webservice role or webhook read access. Yes. Set the environment to LIVE and provide your live URL prefix from the Adyen Customer Area. Test thoroughly in the TEST environment first, since the server is still in alpha and tools may change. Yes. The \`--tools\` option takes a comma-separated list, so a developer agent can get only the webhook tools and a support agent only payment links and session lookups. Fewer tools also make the agent more reliable. The server talks directly to Adyen's APIs, so data flows between your agent and Adyen as with any integration. The model on inference.eu that reads the responses runs in EU data centres, and the API key is stored encrypted in the EU. Yes. Since version 0.6.0, tools carry read-only, idempotent and destructive annotations. inference.eu agents can use these hints to ask a person for approval before destructive calls such as refunds run. [Ask a question](https://inference.eu/contact/) ## Related [All MCP servers](https://inference.eu/connect/#directory) - [MollieConnect inference.eu agents to the official Mollie MCP server. Look up payments, settlements and customers, and create payment links or subscriptions with approval.Banking and payments](https://inference.eu/connect/mollie/) - [StripeConnect inference.eu agents to Stripe's official MCP server to look up customers and payments, create invoices and payment links, and search Stripe docs.Banking and payments](https://inference.eu/connect/stripe/) - [ShopwareConnect inference.eu agents to the MCP server built into Shopware 6. Search products, orders and customers, and update entities within your integration's ACL.ERP](https://inference.eu/connect/shopware/) - [SalesforceConnect inference.eu agents to Salesforce Hosted MCP Servers to query and update records with each user's own permissions, sharing rules and field security.CRM and sales](https://inference.eu/connect/salesforce/) ## Move your AI workloads to EU infrastructure Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps. - Reply within one working day - Pricing for your volume - DPA ready to sign