home / mcp / adyen checkout utility service mcp server

Adyen Checkout Utility Service MCP Server

Provides an MCP interface to the Adyen Checkout Utility Service, enabling multi-agent conversations through a configurable local server.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "bassilkhilo-ag2-adyen-checkout-utility-service": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "A JSON string containing the configuration",
        "SECURITY": "Environment variables for security parameters (e.g., API keys)",
        "CONFIG_PATH": "Path to a JSON configuration file (e.g., mcp_server/mcp_config.json)"
      }
    }
  }
}

You can deploy and run an MCP server that exposes capabilities for interacting with the Adyen Checkout Utility Service. This server lets clients connect in standard MCP patterns, enabling multi-agent conversations and coordinated actions against the Adyen API surface.

How to use

Start the MCP server in one of the supported transport modes. The simplest approach for local development is the stdio mode, which runs the server as a normal Python process and communicates through standard I/O channels. From a client, you connect using the MCP protocol via the stdio transport and issue actions that coordinate with the Adyen Checkout Utility Service. You can also configure a custom environment to point the server at a specific MCP configuration file or inline configuration.

How to install

Prerequisites you need before installing the MCP server are Python 3.9 or later, plus pip and uv.

Step 1. Install Python dependencies manually if you are not using the development container.

pip install -e ".[dev]"

Alternative: use uv to install dependencies in editable mode.

uv pip install --editable ".[dev]"

Step 2. Run the MCP server in stdio mode to start listening for MCP clients.

python mcp_server/main.py stdio

Configuration and environment

Configure the server with environment variables or a configuration file. You can provide a JSON configuration via a file path or a JSON string. The following environment variables are recognized for configuration and security:

- CONFIG_PATH: Path to a JSON configuration file (for example, mcp_server/mcp_config.json).

- CONFIG: A JSON string containing the configuration.

- SECURITY: Environment variables that control security parameters such as API keys.

Running tests and quality checks

The project uses linting, static type checking, and tests to ensure code quality. Run these commands to verify your changes before you commit.

ruff check
ruff format

Static analysis and tests can be run with provided scripts during development.

./scripts/static-analysis.sh
./scripts/test.sh
./scripts/test-cov.sh

Building and publishing

If you need to build or publish artifacts, the project uses Hatch for building and publishing.

hatch build
hatch publish

Notes on usage with MCP clients

When you connect with an MCP client, you can perform coordinated actions against the Adyen Checkout Utility Service. The server runs as a local process in stdio mode and reads its configuration from the specified path or inline JSON. Ensure your client and server share a compatible MCP protocol version and that security credentials (if used) are correctly provisioned.

Tools and scripts referenced

The project includes utilities for linting, static analysis, testing, and packaging. These tools help you maintain code quality and deploy reliably.