This Mollie MCP Server acts as a bridge between your Mollie account and a language model through the MCP protocol. It exposes a set of tools that let you fetch recent Mollie transactions, retrieve detailed information about a specific transaction, list available payment methods, generate payment links, and inspect your Mollie profile information. Clients can call these tools from natural language prompts to get up-to-date Mollie data without building custom UIs. To use it, run the server with your Mollie API key and connect your MCP client to the configured server. The tools you can invoke are: fetch-transactions to retrieve recent payments; transaction-info to get full details of a specific transaction (paymentId starting with tr_); fetch-methods to obtain supported payment methods; profile-info to get current Mollie profile data; and create-payment-link to generate a Mollie payment URL for a specified amount.

Prerequisites:

• Node.js and npm installed
• Access to a Mollie account with an API key

Steps:

1. Clone the repository and install dependencies: git clone https://github.com/hreinberger/mollie-mcp.git cd mollie-mcp npm install

2. Configure environment variables:

   • Copy the example environment file and edit it with your keys: cp .env.example .env

     Edit .env and set MOLLIE_API_KEY and MOLLIE_API_MODE as needed

3. Build the project: npm run build This compiles TypeScript in src/ to JavaScript in build/.

4. Run the MCP server:

   • Ensure the Mollie API key is set in your environment (or in a .env load step).
   • Start the server (example): node build/index.js

5. Connect an MCP client:

   • Use a client that supports MCP and point it to the running server configuration (e.g., in .vscode/mcp.json or your client equivalent).
   • Example client config may reference: { "servers": { "mollie-mcp": { "type": "stdio", "command": "node", "args": ["<absolute-path-to-repo>/build/index.js"] } } }

Tips:

• Keep your Mollie API key secure and do not commit it to version control.
• The server loads environment variables from .env; ensure they are present when running locally.
• If you encounter token bloat from full Mollie objects, consider adjusting the client prompts or implementing result truncation on the client side.
• The available tools can be extended; currently supported: fetch-transactions, transaction-info, fetch-methods, profile-info, and create-payment-link.
• If using test mode, ensure you have a test API key from Mollie and that your Mollie account is configured for test transactions.