mcpSource-backedReview first Safety ✓ Privacy ✓

Adyen MCP Server for Claude

Integrate with Adyen's payment platform from Claude — create payment sessions and links, cancel/refund payments, manage terminals, webhooks, API credentials, and merchant accounts — with the official Adyen Model Context Protocol server covering Checkout and Management APIs.

by Adyen·added 2026-06-18·

Claude Code Codex Cursor Claude Desktop

HarnessClaude CodeCodexCursorClaude Desktop

Install

Source

claude mcp add adyen -- npx -y @adyen/mcp --adyenApiKey=YOUR_ADYEN_API_KEY --env=TEST

Readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedYes

Documentation Source repository Registry JSON · LLM text

Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

This server can create payment sessions, generate payment links, cancel authorized payments, and initiate refunds — these are live financial operations.
Use `--env=TEST` during development with Adyen's test API keys to avoid live transactions.
Restrict enabled tools to only what is needed via the `--tools` parameter (e.g., `--tools=create_session,list_merchants`).

Privacy notes

Payment session data, merchant account details, terminal configurations, and webhook payloads from your Adyen instance are surfaced in Claude's context.
Your Adyen API key is passed as a CLI argument — use environment variable substitution (e.g., `--adyenApiKey=${ADYEN_API_KEY}`) to avoid exposing it in config files.

Prerequisites

An Adyen account with a web service API key (customer area → Developers → API credentials).
The API key user must have appropriate roles: Checkout Webservice, Management API - Accounts Read, Merchant PAL Webservice, and others depending on tools used (see docs).
Node.js with `npx` available.
An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 15 minutes
Difficulty: intermediate

Tool listing metadata

Website: https://adyen.com
Disclosure: Adyen is a commercial global payment platform. The MCP server is officially maintained by Adyen.

Full copyable content

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

About this resource

Overview

The Adyen MCP Server is the official Model Context Protocol server from Adyen, one of the world's leading global payment platforms. It gives Claude access to both the Adyen Checkout API (payment sessions, payment links, refunds, cancellations) and the Adyen Management API (merchant accounts, terminals, webhooks, payment methods, API credentials, users). The server supports scoping active tools to only those needed for a given workflow via --tools. Licensed under MIT.

Key capabilities

Checkout API — create payment sessions, get session results, list payment methods, create and update payment links.
Payments modification — cancel authorized payments and refund captured payments.
Terminal management — list terminals, reassign terminals, manage Android apps, terminal settings, and terminal actions.
Webhooks — list, get, and test webhooks at company and merchant levels.
Management API — list merchant accounts, payment method settings, API credentials, and allowed origins.

Tools (40+)

Category	Tools
Checkout — Sessions	`create_session`, `get_session`, `get_payment_methods`
Checkout — Payment Links	`create_payment_link`, `get_payment_link`, `update_payment_link`
Checkout — Modifications	`cancel_payment`, `refund_payment`
Terminals	`list_terminals`, `reassign_terminal`, `get_terminal_settings`, `update_terminal_settings`
Webhooks	`list_company_webhooks`, `list_merchant_webhooks`, `test_webhook`
Accounts	`list_merchants`
Payment Methods	`list_payment_method_settings`
API Credentials	`list_api_credentials`

How it compares

Server	Sessions	Payment links	Refunds	Terminal mgmt	Webhooks
Adyen MCP	Yes	Yes	Yes	Yes	Yes
Stripe MCP	Yes	Yes	Yes	No	Limited
Razorpay MCP	No	Yes	Yes	No	No
Square MCP	Yes	Yes	Yes	Limited	Limited

Adyen's terminal management tools — for point-of-sale hardware, Android apps, and terminal settings — are unique among payment MCP servers.

Installation

Test environment (recommended to start)

claude mcp add adyen -- npx -y @adyen/mcp \
  --adyenApiKey=YOUR_ADYEN_API_KEY \
  --env=TEST

Live environment

claude mcp add adyen -- npx -y @adyen/mcp \
  --adyenApiKey=YOUR_ADYEN_API_KEY \
  --env=LIVE \
  --livePrefix=YOUR_LIVE_URL_PREFIX

Scoping tools

npx -y @adyen/mcp \
  --adyenApiKey=YOUR_ADYEN_API_KEY \
  --env=TEST \
  --tools=create_session,get_payment_methods,create_payment_link

Requirements

An Adyen account with a webservice API key.
Node.js with npx.
An MCP client (Claude Code or Claude Desktop).

Security

Always start with --env=TEST to test with Adyen's sandbox before enabling live operations.
Scope tools with --tools to apply least-privilege access.
Pass the API key via environment variable substitution rather than hardcoding it.

Source Verification Notes

Verified on 2026-06-18:

Official GitHub repository adyen/adyen-mcp (MIT) documents the @adyen/mcp npm package, --adyenApiKey, --env=TEST/LIVE, --livePrefix, and --tools CLI parameters, all 40+ tools across Checkout API, Management API, terminal management, and webhooks, plus the required webservice user roles.
Adyen documentation at docs.adyen.com/development-resources/mcp-server/ (HTTP 200) covers setup, authentication, and tool availability.
Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector pattern used above.

#adyen #payments #payment-links #checkout #terminals #fintech #webhooks

Source citations

Add this badge to your README

Show that Adyen MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/adyen-mcp-server.svg)](https://heyclau.de/entry/mcp/adyen-mcp-server)

How it compares

Adyen MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Adyen MCP Server for Claude Integrate with Adyen's payment platform from Claude — create payment sessions and links, cancel/refund payments, manage terminals, webhooks, API credentials, and merchant accounts — with the official Adyen Model Context Protocol server covering Checkout and Management APIs. Open dossier	Razorpay MCP Server for Claude Automate payments, orders, refunds, settlements, and Razorpay checkout integrations from Claude with the official Razorpay MCP Server — hosted remotely at mcp.razorpay.com or self-hosted, covering 40+ payment API tools for South Asia's leading payments platform. Open dossier	Agentic Terminal Directory MCP Server for Claude AT Directory hosted MCP server for discovering Observer Protocol–verified merchants accepting Lightning, BOLT12, L402, and USDT agentic payments with live rail verification. Open dossier	Aiven MCP Server for Claude Manage your Aiven cloud database services from Claude — list and monitor PostgreSQL, Apache Kafka, ClickHouse, Valkey, and OpenSearch services, execute SQL queries, manage Kafka topics and schemas, tail logs, and optimize queries — with the official Aiven MCP server. Open dossier
Trust
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Category	mcp	mcp	mcp	mcp
Source	source-backed	source-backed	source-backed	source-backed
Author	Adyen	Razorpay	Observer Protocol	Aiven
Added	2026-06-18	2026-06-18	2026-06-14	2026-06-18
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓This server can create payment sessions, generate payment links, cancel authorized payments, and initiate refunds — these are live financial operations. Use `--env=TEST` during development with Adyen's test API keys to avoid live transactions. Restrict enabled tools to only what is needed via the `--tools` parameter (e.g., `--tools=create_session,list_merchants`).	✓The server can create orders, capture payments, create refunds, and generate payment links — these are live financial operations on your Razorpay account. Use test mode credentials (key IDs starting with `rzp_test_`) during development to avoid real charges. Treat your Razorpay Key Secret and Base64-encoded credentials as sensitive secrets — do not commit them to version control.	✓The directory indexes merchant claims and attestations; verify rails before sending funds. `verify_payment_endpoint` probes live endpoints but agents still pay merchants directly. Tier 1 merchants are self-attested; prefer Tier 2+ records for high-value purchases. Never share private keys or wallet seeds through MCP chat sessions.	✓Write operations (create/update services, deploy apps) are available but require `AIVEN_READ_ONLY=false` — the server defaults to read-only mode. Aiven services include managed production databases — confirm before creating or modifying services.
Privacy notes	✓Payment session data, merchant account details, terminal configurations, and webhook payloads from your Adyen instance are surfaced in Claude's context. Your Adyen API key is passed as a CLI argument — use environment variable substitution (e.g., `--adyenApiKey=${ADYEN_API_KEY}`) to avoid exposing it in config files.	✓Payment details, customer information, refund records, and settlement reports from your Razorpay account are surfaced in Claude's context. The remote MCP server is hosted by Razorpay — requests go through Razorpay's infrastructure; review Razorpay's privacy policy for data handling.	✓Search queries and merchant IDs may appear in Agentic Terminal logs. Payment transactions occur directly with merchants, not through the directory. Optional credentials link your agent identity for rate-limit and review features.	✓Service metadata, metrics, application logs, PostgreSQL query stats, Kafka topic configurations, and Schema Registry content from your Aiven account are surfaced in Claude's context. Your `AIVEN_TOKEN` grants account-level API access — keep it in the MCP config env and never commit it to version control.
Prerequisites	An Adyen account with a web service API key (customer area → Developers → API credentials). The API key user must have appropriate roles: Checkout Webservice, Management API - Accounts Read, Merchant PAL Webservice, and others depending on tools used (see docs). Node.js with `npx` available. An MCP client such as Claude Code or Claude Desktop.	A Razorpay account with Key ID and Key Secret from the Dashboard → Settings → API Keys. Base64-encode your credentials: `echo -n 'key_id:key_secret' \| base64` and use the result as the Authorization value. Node.js with `npx` installed. An MCP client such as Claude Code or Claude Desktop.	MCP client with streamable HTTP connector support. Understanding that the directory is discovery-only—not in the payment path. Optional Observer Protocol DirectoryAccessCredential for higher rate limits and write access. Wallet or payment rail tooling separate from the directory for actual checkout.	An Aiven account — sign up at aiven.io. An Aiven API token: User Information → Authentication → Generate Token. Node.js with `npx` available. An MCP client such as Claude Code or Claude Desktop.
Install	`claude mcp add adyen -- npx -y @adyen/mcp --adyenApiKey=YOUR_ADYEN_API_KEY --env=TEST`	`claude mcp add razorpay -e AUTH_HEADER="Basic YOUR_BASE64_KEY_SECRET" -- npx mcp-remote https://mcp.razorpay.com/mcp --header "Authorization:${AUTH_HEADER}"`	`claude mcp add --transport http at-directory https://mcp.agenticterminal.ai/mcp`	`claude mcp add --scope user aiven-mcp -e AIVEN_TOKEN=<your-token> -- npx -y mcp-aiven`
Config	`{ "mcpServers": { "adyen": { "command": "npx", "args": [ "-y", "@adyen/mcp", "--adyenApiKey=YOUR_ADYEN_API_KEY", "--env=LIVE", "--livePrefix=YOUR_LIVE_URL_PREFIX" ] } } }`	`{ "mcpServers": { "razorpay": { "command": "npx", "args": [ "mcp-remote", "https://mcp.razorpay.com/mcp", "--header", "Authorization: Basic ${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "YOUR_BASE64_ENCODED_KEY_SECRET" } } } }`	`{ "mcpServers": { "at-directory": { "url": "https://mcp.agenticterminal.ai/mcp", "type": "http", "headers": { "Authorization": "Bearer YOUR_DIRECTORY_ACCESS_CREDENTIAL" } } } }`	`{ "mcpServers": { "aiven-mcp": { "command": "npx", "args": ["-y", "mcp-aiven"], "env": { "AIVEN_TOKEN": "<your-token>", "AIVEN_READ_ONLY": "false", "AIVEN_SERVICES_SCOPE": "kafka,pg" } } } }`
Citations	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationdocs.adyen.com Websiteadyen.com	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationgithub.com	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationagenticterminal.ai Submitted by kiannidev2026-06-14	Source repositorygithub.com 2026-06-18T07:06:04+00:00 Documentationaiven.io
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Signals

Loading live community signals…

Safety notes

Privacy notes

Prerequisites

Schema details

About this resource

Overview

Key capabilities

Tools (40+)

How it compares

Installation

Test environment (recommended to start)

Live environment

Scoping tools

Requirements

Security

Source Verification Notes

Source citations

Add this badge to your README

How it compares

Related resources

Razorpay MCP Server for Claude

Agentic Terminal Directory MCP Server for Claude

Aiven MCP Server for Claude

Arize Phoenix MCP Server for Claude

Signals