MCP Ecommerce

Installation guide

How to install Adyen MCP Server

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

Adyen's MCP server is a local install. You run it on your own machine with `npx`, passing an Adyen API key and an environment flag (`TEST` or `LIVE`). There is no hosted URL and no browser sign-in. The server is an alpha release and currently covers the Checkout API and Management API only.

A developer who already administers the Adyen account should do this, using an API credential created for this purpose. Start in the test environment. Live mode sends real requests that can move real money, so use it only for supervised tasks after testing.

Adyen MCP Server setup guide: Adyen's MCP documentation page on docs.adyen.com, shown in a browser frame (payments MCP server for e-commerce)
Adyen MCP Server setup guide preview: Adyen’s documentation on docs.adyen.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

  • An Adyen account where you can create or view an API credential and generate an API key, as described in the Adyen API credentials documentation.
  • The roles listed in the vendor docs on that credential: Merchant PAL webservice, Checkout webservice, and the Management API roles for payment methods, account, terminals, terminal actions, Android files and terminal settings.
  • Node.js with npx available on the machine that will run the server.
  • For live mode only: your live URL prefix, found in the live Customer Area under Developers > API URLs > Prefix.
  • An LLM client that supports local MCP servers, such as Claude Desktop, Cursor, Claude Code, Gemini CLI or VS Code.
How it runs
Local, runs on your machine
Access
Read and write
Server address
Copy it from the vendor documentation

Adyen MCP Server in Claude

  1. Create an API key for a dedicated Adyen credential and confirm the roles listed in the vendor documentation are assigned.
  2. Open Claude Desktop and go to Settings > Developer > Edit Config to open claude_desktop_config.json. The Adyen docs do not cover this client, so this is the standard local-server route.
  3. Add an adyen entry under mcpServers using the snippet below, replacing ADYEN_API_KEY with your key and keeping --env=TEST.
  4. Save the file and fully restart Claude Desktop.
  5. Check that the Adyen tools are listed, then run a read-only prompt from the verify section.
  6. Remote connectors by URL do not apply, because this server runs locally.
claude_desktop_config.json
{
  "mcpServers": {
    "adyen": {
      "command": "npx",
      "args": [
        "-y",
        "@adyen/mcp",
        "--adyenApiKey=ADYEN_API_KEY",
        "--env=TEST"
      ]
    }
  }
}

Adyen MCP Server in ChatGPT

  1. The Adyen docs do not cover ChatGPT. ChatGPT connectors in Developer mode expect a remote MCP server URL, and this server runs locally with no hosted endpoint.
  2. Do not publish the local process to the internet just to connect it. Exposing a server that holds an Adyen API key is a security risk.
  3. Use a client that can launch a local command instead, such as Claude Desktop, Cursor, Claude Code or VS Code.
  4. If you still need ChatGPT, check the Adyen documentation and GitHub repository for any remote option before proceeding.

Adyen MCP Server in Gemini

  1. Create a dedicated Adyen API key and confirm the required roles. The Adyen docs do not cover Gemini, so this uses the standard Gemini CLI route.
  2. Open the Gemini CLI settings file (settings.json) and add an mcpServers entry named adyen.
  3. Use the snippet below, replacing ADYEN_API_KEY with your key and keeping --env=TEST.
  4. Restart Gemini CLI and list the MCP servers to confirm adyen is connected.
  5. Run a read-only prompt from the verify section.
  6. Gemini app extensions are not covered by the docs, so do not rely on them for this server.
Gemini CLI settings.json
{
  "mcpServers": {
    "adyen": {
      "command": "npx",
      "args": [
        "-y",
        "@adyen/mcp",
        "--adyenApiKey=ADYEN_API_KEY",
        "--env=TEST"
      ]
    }
  }
}

Adyen MCP Server in Microsoft Copilot

  1. Create a dedicated Adyen API key and confirm the required roles. The Adyen docs do not cover Copilot.
  2. For GitHub Copilot in VS Code, create .vscode/mcp.json in your workspace and add an adyen entry under servers using the snippet below.
  3. Replace ADYEN_API_KEY with your key. Do not commit the file with a real key in it.
  4. Start the server from the editor's MCP controls and confirm the Adyen tools appear in Copilot's agent mode tool list.
  5. Microsoft Copilot Studio expects a remote MCP endpoint, which this local server does not provide, so the docs give no route for it.
.vscode/mcp.json
{
  "servers": {
    "adyen": {
      "command": "npx",
      "args": [
        "-y",
        "@adyen/mcp",
        "--adyenApiKey=ADYEN_API_KEY",
        "--env=TEST"
      ]
    }
  }
}

Adyen MCP Server in Perplexity

  1. The Adyen docs do not cover Perplexity.
  2. In the Perplexity desktop app, open the connectors settings and look for an option to add a local MCP server by command. Availability depends on your app version and plan.
  3. If it is offered, enter npx with the arguments -y @adyen/mcp --adyenApiKey=ADYEN_API_KEY --env=TEST, using your real key.
  4. If only remote connectors by URL are available, this server cannot be added there. Use another client from this guide.
  5. Once connected, run a read-only prompt from the verify section.

Adyen MCP Server in Cursor

  1. Create a dedicated Adyen API key and confirm the required roles. The Adyen docs do not cover Cursor, so this is Cursor's standard local-server route.
  2. Open Cursor Settings > MCP and add a new server. This edits mcp.json, either project-level at .cursor/mcp.json or global.
  3. Paste the snippet below, replacing ADYEN_API_KEY with your key and keeping --env=TEST.
  4. Save and confirm the adyen server shows as enabled with its tools listed.
  5. Run a read-only prompt from the verify section.
mcp.json
{
  "mcpServers": {
    "adyen": {
      "command": "npx",
      "args": [
        "-y",
        "@adyen/mcp",
        "--adyenApiKey=ADYEN_API_KEY",
        "--env=TEST"
      ]
    }
  }
}

Adyen MCP Server in Claude Code

  1. Create a dedicated Adyen API key and confirm the required roles. The Adyen docs do not cover Claude Code, so this uses its standard claude mcp add form for local servers.
  2. Run the command below in a terminal, replacing ADYEN_API_KEY with your key.
  3. Run claude mcp list to confirm adyen is registered.
  4. Start claude and use /mcp to check the server status.
  5. Run a read-only prompt from the verify section.
Terminal
claude mcp add adyen -- npx -y @adyen/mcp --adyenApiKey=ADYEN_API_KEY --env=TEST

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

  • List the tools available from the Adyen MCP server and say which ones only read data.
  • Look up my Adyen test account's available payment methods. Do not change anything.
  • Show the terminal settings for my Adyen test account, read-only.

Troubleshooting

+The client does not list the Adyen server or its tools. What should I check?

Confirm that `npx` is on the PATH the client uses, since GUI apps can differ from your shell. Check the config JSON is valid and the client was fully restarted. Run `npx -y @adyen/mcp --adyenApiKey=ADYEN_API_KEY --env=TEST` in a terminal to see startup errors.

+Requests fail with permission or authorization errors. Why?

The API key's credential probably lacks a required role. Check that Merchant PAL webservice, Checkout webservice and the listed Management API roles are assigned. Also confirm the key belongs to the environment you started with: a TEST key with `--env=LIVE`, or the reverse, will fail.

+Live mode will not start or calls fail. What is missing?

Live mode needs `--env=LIVE` and `--livePrefix=YOUR_PREFIX_URL` in addition to the API key. Take the prefix from the live Customer Area under `Developers > API URLs > Prefix`. Use a live API key, and run only supervised tasks, because live calls can move real money.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.