Adyen MCP Server – Payments API Integration
The Adyen MCP Server lets LLM clients interact with supported Adyen APIs through Model Context Protocol tools. It is useful for payment-platform development, testing, and operational workflows such as creating payment sessions, payment links, refunds, merchant lookups, terminal actions, webhook checks, and payment-method discovery.
Overview
The Adyen MCP Server is an official Adyen TypeScript MCP server for integrating Adyen APIs into LLM clients. It runs locally and exposes a set of tools that convert natural-language requests from an MCP client into supported Adyen API calls. The server is intended for developers and operations teams working with Adyen payment integrations who want an AI assistant to use real Adyen account context instead of relying only on static documentation.
What the MCP server enables
The server currently supports tools around Adyen Checkout and Management APIs. Documented examples include creating Checkout /sessions payment requests, retrieving payment-session results, listing available payment methods, creating and checking payment links, expiring payment links, cancelling authorized payments, refunding captured payments, listing merchant accounts, listing and reassigning terminals, reading Android app and certificate information, scheduling and listing terminal actions, reading or updating terminal settings, listing and testing webhooks, listing users, listing API credentials, and listing allowed origins.
Because these tools call Adyen APIs, the AI agent can perform real actions when the API credential has the required roles. Access should be scoped carefully, especially for payment modification, terminal settings, webhook testing, or management operations.
When to use it
Use this MCP server when building, testing, or operating Adyen integrations with an MCP-capable assistant. Practical workflows include asking an assistant to create a test payment link, check a payment-link status, retrieve available payment methods for a checkout flow, inspect webhooks during troubleshooting, or refund a captured payment after validating the order context.
Connection and authentication
Adyen documents the server as a local stdio MCP server started with npx -y @adyen/mcp. For the test environment, pass an Adyen API key and --env=TEST. For live use, pass --env=LIVE and the Adyen live URL prefix with --livePrefix. Adyen recommends creating a dedicated webservice user and API key for the MCP application, then limiting the assigned roles to the exact tools needed.
Key considerations
The Adyen MCP Server is marked as alpha in the official GitHub repository. It does not expose every Adyen API endpoint; Adyen documents a current supported set and says more APIs and endpoints are being added. Treat the MCP server as an API client with the same security impact as any other Adyen integration: use least-privilege roles, separate test and live credentials, avoid embedding real secrets in configuration files, and restrict tool selection with --tools when only a subset of operations is needed.
Supported Transports
stdio
Command: npx
Args:
-y@adyen/mcp--adyenApiKey=${ADYEN_API_KEY}--env=TEST
Frequently Asked Questions
- When should an AI agent use the Adyen MCP Server?
- Use it when an MCP-capable assistant needs to work with supported Adyen Checkout or Management API workflows, such as creating payment links, checking payment sessions, listing payment methods, inspecting webhooks, or managing terminal-related tasks.
- What does the Adyen MCP Server add to an AI agent's capabilities?
- It gives the agent live tool access to documented Adyen API operations instead of only general knowledge, allowing prompts to be translated into specific Adyen API requests through function calling.
- What can the AI agent access or manage through this server?
- Official documentation lists support for Checkout sessions, payment methods, payment links, cancellations, refunds, merchant accounts, terminals, Android terminal assets, terminal actions and settings, webhooks, users, API credentials, and allowed origins, subject to the roles on the configured Adyen API credential.
- How is authentication configured for the Adyen MCP Server?
- The local server is started with an Adyen API key, commonly passed through the `ADYEN_API_KEY` environment variable and the `--adyenApiKey` argument. For live use, Adyen also requires the live URL prefix. Adyen recommends a dedicated webservice user and least-privilege roles for MCP use.
- Which transport should be used for the Adyen MCP Server?
- Use the documented local `stdio` transport by starting `npx -y @adyen/mcp`. The official setup shown by Adyen uses a local stdio server; this YAML does not include remote HTTP or SSE endpoints because they are not documented as supported connection methods for this provider.