Adyen MCP Server

npx -y @adyen/mcp --env=TEST

{
  "mcpServers": {
    "adyen-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@adyen/mcp",
        "--env=TEST"
      ]
    }
  }
}

The server runs over stdio from npx @adyen/mcp and refuses to start without an --env flag choosing TEST or LIVE; the live path additionally needs your live URL prefix, which is the piece of Adyen's setup people most often forget. Tools split between the Checkout API, where you create sessions, list payment methods, issue and force-expire payment links and cancel or refund captured payments, and the Management API, where merchant accounts, terminals and their settings, webhooks, users and API credentials are readable. Adyen maps each tool onto a specific webservice role and recommends a dedicated user carrying only the roles you actually need; a --tools flag loads a named subset so the credential scope and the exposed surface stay aligned. It is labelled alpha, which is worth weighing before wiring write operations to a live account.