Article
Powering effortless integrations: Introducing Adyen’s Model Context Protocol server
We are piloting our MCP server to empower developers to build their payments integration with Adyen using large language models (LLMs). Learn more about our MCP and how to get started in this article.
At Adyen, we build financial technology that empowers businesses to thrive in global commerce. To continuously innovate how businesses interact with our platform, we are releasing the alpha version of our Model Context Protocol (MCP) server to support seamless integrations. This new solution is designed to bridge the gap between large language models (LLMs) and our APIs.
What can Adyen’s MCP server do for you?
For Adyen customers, the MCP server introduces a more intuitive and efficient way to manage financial operations. With our MCP, we aim to empower developers to integrate advanced payment functionalities simply by expressing their needs in natural language, without having to write code for each API interaction. For instance, a developer could prototype a system where a customer service agent types "Initiate a full refund for order #12345" and the MCP server translates this into the correct Adyen API calls.
This first iteration aims to streamline common financial workflows, such as creating payment sessions, managing payment links, or processing cancellations and refunds, by making these actions accessible through conversational AI. The Adyen MCP server is designed to understand your intent, translate it into API calls, and execute various actions, ultimately unlocking new types of integrations and providing developers with more tools to integrate, test and validate.
Our goal is to make our powerful financial technology platform accessible via conversational AI, opening doors to faster development cycles and innovative applications.
How the Adyen MCP works
At its core, the Adyen MCP server leverages LLM function calling to enable a new way of interacting with Adyen's comprehensive suite of APIs. This allows for a more natural, intent-driven approach to integrating payment and financial functionalities. Imagine interacting with a system that can understand your request, translate it into API requests, and execute the correct financial actions. This will make integrating with our financial platform much more simpler.
Initial tools and use cases
Through this pilot, we are exploring how the MCP Server can simplify and enhance business operations for enterprise fintech integrations. The alpha release supports interactions with an initial set of key Adyen APIs and endpoints, including the Checkout and Management APIs. Find all supported endpoints in our documentation.
The background: bridging LLMs and APIs
The MCP is an open-source protocol that standardizes how applications provide context to LLMs. Its structured approach to LLM function calling has significant industry attention, making it a valuable standard to enable agentic capabilities. Our adoption of the MCP is a testament to the broader industry trend.
Recognizing this potential, we are exploring how to let LLMs interact with our comprehensive financial platform in a structured and secure manner to empower seamless integrations. The MCP server addresses the challenge of integrating, providing a robust, intermediary layer that translates natural language prompts into actionable operations.
Next steps: a pilot for innovation
For developers, our MCP introduces a new standard to build integrations with Adyen. We're stepping into a new paradigm where financial functionality can be easily integrated. It's important to understand that the Adyen MCP server is currently in alpha version. While the possibilities are incredibly promising, we’re still exploring what the technology can do for our customers on a day-to-day basis.
We are excited to see what you will build! Read our guide to get started with the MCP. If you want to share feedback, please contact your Adyen contact or reach out to us by sending an email to devrel@adyen.com.
Stay tuned for more insights and updates as we progress!