# mcp-adyen [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/codespar/mcp-dev-latam  
**GitHub Stars:** 274  
**npm Downloads (last month):** 123  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-adyen

## Description
MCP server for Adyen Checkout API v71 — enterprise payments (iFood, Uber, Spotify in LatAm)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-adyen": {
    "command": "npx",
    "args": ["-y","@codespar/mcp-itau@alpha"]
  }
}
```

## Documentation

## What mcp-adyen MCP server does

The mcp-adyen MCP server connects an MCP-compatible AI agent to Adyen Checkout API v71. Its scope is enterprise payments, with the repository description positioning it for commerce operations associated with services such as iFood, Uber, and Spotify in Latin America.

Adyen is one of several commerce and payment systems represented in the wider MCP Dev LATAM repository. The repository groups its servers around payments, fiscal services, logistics, messaging, banking, ERP, identity, fraud, crypto, and agentic payment protocols. This server is specifically the Adyen entry, rather than a general-purpose gateway for every provider in that catalog.

Use it when the payment provider behind an agent workflow is Adyen and the workflow needs to be presented through MCP. It may be a better fit than the repository's regional payment servers when an existing business relationship or payment integration already relies on Adyen Checkout.

## How it works

The server acts as an MCP interface over Adyen Checkout API v71. An MCP client starts the server and makes its exposed payment capabilities available to an AI agent. The agent can then request supported Adyen operations through the client instead of calling the provider API directly from its own application logic.

Those details should be checked in the package documentation or source before planning a workflow around a particular payment operation.

This design places the server in the repository's MCP tool layer: the agent-facing interface sits between an application workflow and the underlying payment service. It is distinct from the repository's separate Stripe ACP, Google UCP, AP2, and x402 packages, which address agentic commerce, authorization, or micropayment protocol use cases.

## Tools and capabilities

The mcp-adyen MCP server is documented as an Adyen Checkout API v71 server for enterprise payments.

Do not assume those functions are available without confirming the server's current package or source documentation. The same caution applies to authentication modes, webhook support, payment methods, regional coverage, and idempotency behavior.

## Limitations and notes

The repository description supplies a provider and API version, but not setup instructions specific to mcp-adyen.

The examples naming iFood, Uber, and Spotify establish the intended enterprise-payment context; they do not document those companies as built-in integrations or guarantee access to their accounts. Deployment still depends on the relevant Adyen account, credentials, permissions, and API availability.

The repository is published under the MIT License. Verify those details before selecting it for production use.

_Full upstream README: https://allmcps.com/mcp/mcp-adyen/readme_