Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 1
- 4 8
- 3 4
- 2 6
- 1 0
Trust in production
- Trust it - 21%
- With caveats - 47%
- Wouldn't - 32%
53% would recommend this server
How reviewers scored it
- Setup & docs 3.3
- Auth experience 3.3
- Reliability 3.1
- Maintainer responsiveness 3.6
Why it got a C
Adyen's official server, still labelled alpha. It runs locally over stdio and takes an API key from a webservice user, and that user's roles decide which calls work. Its tools can refund and cancel payments, create payment links, reassign terminals and change terminal settings. Adyen advises a dedicated user with only the roles you need, plus --tools to load a subset. Start with --env=TEST. Biggest deduction: the last release (0.6.0) was in August 2026, and auth is a long-lived API key, not revocable OAuth.
How to connect
// .vscode/mcp.json (README example)
{
"servers": {
"adyen-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@adyen/mcp", "--env=TEST"],
"env": {
"ADYEN_API_KEY": "${ADYEN_API_KEY}"
}
}
}
}Is Adyen MCP Server safe?
Is Adyen MCP Server safe to use?
Adyen MCP Server grades C (usable with care). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. Updates are occasional, so fixes may be slow to arrive. It runs locally over stdio, so it acts with your machine's access.
Does Adyen MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Adyen MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Payments & Billing
- A Stripe MCPOfficial hosted Stripe server for customers, payments, invoices, subscriptions, and refunds.
- B PayPal MCP ServerOfficial PayPal server for invoices, orders, refunds, disputes, and subscriptions.
- B Square MCP ServerOfficial Square server exposing the full Square API (payments, orders, catalog, refunds).
Embed this badge
[](https://trustedmcp.io/servers/adyen-mcp)<a href="https://trustedmcp.io/servers/adyen-mcp"><img src="https://trustedmcp.io/badge/adyen-mcp.svg" alt="TrustedMCP grade C" height="80"></a>Community reviews
Clean integration, sensible permissions
Replaced a homegrown script with Adyen MCP Server and have not looked back. Updates are a bit slow, but it is stable enough that it has not mattered. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Good choice if you need Adyen in your agent.
Used for Answering billing questions from customers
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Trustworthy enough for real work
Simple to set up in Cursor, simple to reason about. Issues get answered eventually. Not fast, not abandoned.
Used for Testing checkout flows in test mode
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Worth the five minutes to set up
Tried it on a side project first, then rolled it out at work. You create a token and pass it in. Scope it narrowly, that is the main thing. The API key sits in the config file, so I made a dedicated key with minimal permissions.
Used for Reconciling refunds
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Needs more maintenance love
Not what I expected from the description. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. The OAuth flow worked first time in Claude Code. For anything real I would look elsewhere.
Used for Looking up failed payments for support
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Solid core, fiddly setup
I like it, with reservations. You create a token and pass it in. Scope it narrowly, that is the main thing.
Used for Testing checkout flows in test mode
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
Our agents call this dozens of times a day. Local stdio process, easy to start and stop from the client. I would use it in prod, but only with a human approving writes.
Used for Investigating disputes
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Recommended it to two teams already
Set this up for our team after comparing a few options. Release pace is moderate, so I pin a version and check in monthly. The OAuth flow worked first time in Claude Code. You create a token and pass it in. Scope it narrowly, that is the main thing. Keep permissions tight and it is a good tool.
Used for Reconciling refunds
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Surprisingly polished
Installed it on a Friday, it was part of my workflow by Monday. Updates are a bit slow, but it is stable enough that it has not mattered.
Used for Testing checkout flows in test mode
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Handy for dev, careful in prod
Works well enough for what I need. Updates are a bit slow, but it is stable enough that it has not mattered. You create a token and pass it in. Scope it narrowly, that is the main thing. I will check back in a few releases.
Used for Investigating disputes
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Mixed feelings after two weeks
It does the job, but it took some tweaking. The OAuth flow worked first time in Claude Code. You create a token and pass it in. Scope it narrowly, that is the main thing. Worth it, just do not skip the hardening steps.
Used for Investigating disputes
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 2/5
Too many sharp edges
I wanted to like this one. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Not something I would put in production yet.
Used for Looking up failed payments for support
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Our team uses it every day
Started with it as an experiment, now it is a fixture. Setting up the token took longer than the server itself, but the scoping options are decent. Being official from Adyen counts for a lot when I pitch it to security. Release pace is moderate, so I pin a version and check in monthly. Happy to run it in production.
Used for Answering billing questions from customers
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Would not run this unattended
Gave it a fair shot over two weeks. Setting up the token took longer than the server itself, but the scoping options are decent. Gave it its own API key so I can revoke it without breaking anything else.
Used for Monthly revenue summaries
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Fine once configured properly
Good for experimenting, still deciding about production. Release pace is moderate, so I pin a version and check in monthly.
Used for Looking up failed payments for support
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 2/5
Too much access for my comfort
It works in a demo, but things got shaky under real use. You create a token and pass it in. Scope it narrowly, that is the main thing. Local stdio process, easy to start and stop from the client. Issues get answered eventually. Not fast, not abandoned. Keeping it to local experiments for now.
Used for Monthly revenue summaries
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Fine for a demo, not for prod
Setup was rough and the result was flaky. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Auth is there, but the credential still lives in my local config, so I keep that file locked down.
Used for Reconciling refunds
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Went back to calling the API directly
Ran into problems pretty quickly. Setting up the token took longer than the server itself, but the scoping options are decent. Fine in production if you sandbox it.
Used for Testing checkout flows in test mode
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
The Adyen integration I wanted
Clear tool names, sensible outputs, very few surprises. Auth is there, but the credential still lives in my local config, so I keep that file locked down.
Used for Answering billing questions from customers
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Set it up once, forgot about it
Of the Adyen integrations I tried, this one is the most predictable. Gave it its own API key so I can revoke it without breaking anything else. You create a token and pass it in. Scope it narrowly, that is the main thing. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Recommended, with sensible guardrails.
Used for Monthly revenue summaries
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.