Mollie's MCP server exposes 62 well-structured payment processing tools with clear, domain-specific naming and typed input schemas. Most tools have descriptive, actionable descriptions explaining both the 'what' and 'why'. However, tool proliferation (62 total) and some schema inconsistencies (generic request_body in UpdateSubscription, incomplete schema truncations in descriptions) slightly reduce overall quality. The tools demonstrate production-grade API design with proper pagination support, profile filtering, and testmode toggles. Descriptions are substantive and explain use cases, not just API mechanics.
Get the sum, maximum, minimum or average of the payment links within a specific timeframe by providing the starting date and the ending date.
A function to aggregate payment details like summing the amount over a time period. Options include finding the highest, lowest, average and sum of a set of payments.
Cancel a subscription to stop future recurring payments. The cancellation takes effect immediately - no new payments will be created. Any payments already created remain unchanged. Use this when a customer requests to stop their subscription or when ending a service. The subscription status changes to 'canceled' and cannot be reactivated. This endpoint requires the 'subscriptions.write' scope.
Capture funds from an authorized payment. This endpoint is used to manually capture a payment that was created with captureMode: manual. By default, Mollie captures payments automatically, but for payments requiring manual capture, use this endpoint after collecting customer authorization. You can capture the full authorized amount or a partial amount. This endpoint requires the 'payments.write' scope.
Creates a simple minimal representation of a customer. Payments, recurring mandates, and subscriptions can be linked to this customer object, which simplifies management of recurring payments.
UpdateSubscription uses generic 'request_body' object instead of explicit typed parameters, reducing schema clarity and agent guidance
Tool count (62) approaches the upper bound of focused tool design; while still manageable, indicates some API endpoint proliferation
Multiple description truncations in schema definitions (e.g., CreatePayment, SearchPaymentsByDescription) suggest JSON truncation in data extraction
Some tool names use verbose naming conventions (e.g., 'ListPaymentsFromGivenIDOnwards', 'ListPaymentsWithinSpecifiedTimeInterval') that could be simplified
'GetOrganizationDetails' description is terse ('Get organization ID and organization name') lacking context about use case
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-04-14 | C | 62 | 2025-11-25 | v1 |
Create a new mandate for a customer to authorize recurring payments. IMPORTANT: In most cases, mandates are created automatically when a customer makes their first payment. Manual mandate creation is only needed for specific use cases like importing existing mandates or creating SEPA Direct Debit mandates with pre-existing authorization. Requires the customer's name and payment method details (IBAN for direct debit, card token for credit card, email for PayPal). This endpoint requires the 'mandates.write' scope.
Create a new payment. This tool allows you to create a payment with a specified amount, currency, description, and redirect URL. You can also specify optional parameters such as webhook URL, payment method, profile ID, and capture_mode (set to 'manual' for payments that require manual capture after authorization).
Creates a payment for the customer.
Create a payment link
Create a new recurring payment subscription for a customer. The subscription automatically generates payments at the specified interval (e.g., '1 month', '2 weeks', '1 day'). The customer must have a valid mandate (payment authorization) for recurring charges. You can optionally specify the number of payments (otherwise it runs indefinitely), a start date, and a webhook URL for payment notifications. This endpoint requires the 'subscriptions.write' scope.
Create a new webhook that subscribes to status changes of your resources. Mollie will send HTTP POST requests to your specified URL when events occur.
Retrieve detailed information about a specific balance by its ID. Shows the balance's currency, status, available amount (funds ready to use), pending amount (funds being processed), transfer threshold, and creation date. Use this to check specific currency balance details.
Generate a financial report for a balance over a specific time period. The report shows opening balance, movements (incoming and outgoing funds), and closing balance. Can be grouped by transaction categories or status balances. Useful for accounting, reconciliation, and financial analysis.
Retrieve a specific capture by its ID and the associated payment ID. This endpoint returns detailed information about a single capture, including amount, settlement details, and timestamps.
Given a programming language, it will fetch the relevant Mollie client documentation in that language.
Retrieve a single invoice by its ID. This tool allows you to fetch detailed information about a specific invoice.
Retrieve detailed information about a specific mandate by its ID. This shows the mandate's status, payment method, consumer details (name, account, BIC), signature date, and creation timestamp. Use this to inspect a specific authorization before charging a customer or to verify mandate validity.
Retrieve the next scheduled settlement. The next settlement shows all transactions that are scheduled to be paid out in the upcoming payout cycle. This allows you to preview what amount will be transferred to your bank account and which transactions are included before the settlement is actually processed.
Retrieve the currently open settlement. The open settlement represents all transactions that have been processed but not yet paid out. This is the settlement that is currently accumulating payments and will be included in the next scheduled payout to your bank account.
Get organization ID and organization name
Retrieve a payment by its ID. This tool allows you to fetch detailed information about a specific payment.
Retrieve a single payment link by ID.
Retrieve detailed information about a specific payment method by its ID. Returns 404 if the method is not available on the profile, or 403 if it's available but not yet enabled.
Retrieve your primary balance. The primary balance is your main account balance and is typically in your account's base currency. Shows available funds, pending amounts, and transfer settings. This is the most commonly used balance for most accounts.
Retrieve detailed information about a specific settlement by its ID or bank reference. Returns complete settlement details including the total amount, status, periods breakdown by payment method, and related transaction information. You can use either the Mollie settlement ID (e.g., 'stl_jDk30akdN') or the bank reference (e.g., '1234567.2404.03').
Retrieve detailed information about a specific subscription by its ID. Shows complete subscription details including amount, interval, payment schedule, status, next payment date, remaining payments, creation date, and cancellation date (if applicable). Use this to inspect a subscription before making changes or for customer support inquiries.
Retrieve detailed information about a specific terminal by its ID. This endpoint returns complete details about a single physical point-of-sale device, including its status, brand, model, serial number, currency, and timestamps. This is useful for checking the configuration and status of a specific terminal device.
Retrieve a single webhook by its ID. This tool allows you to fetch detailed information about a specific webhook.
Retrieve a single webhook event by its ID. This returns the full event details including the embedded entity snapshot at the time the event occurred. Requires events.read scope for OAuth authentication.
List all payment methods available on Mollie, regardless of whether they are enabled on the profile. This endpoint shows all methods that Mollie supports, including those not yet activated. The results are not paginated.
List all subscriptions across all customers in your account. Provides an administrative overview of all recurring payment schedules, useful for reporting, analytics, and monitoring overall subscription health. Supports pagination and optional profile filtering.
List all transactions for a specific balance. Shows the transaction history including transaction type, amounts (initial and result), deductions (fees), and timestamps. Useful for auditing, reconciliation, and understanding balance changes over time. Transactions represent movements in and out of the balance.
List all balances in your account. Shows balances for each currency you operate in, including available amounts (ready to use) and pending amounts (being processed). Useful for financial overviews and multi-currency account management.
List all captures for a specific payment. This endpoint returns a paginated list of all captures that have been created for a given payment. Each capture represents funds that have been captured from an authorized payment.
List all subscriptions for a specific customer. Shows all recurring payment schedules associated with a customer, including active, canceled, and completed subscriptions. Each subscription displays the amount, interval, status, next payment date, and remaining payment count. Useful for customer service inquiries and subscription management interfaces.
Retrieve a list of all customers.
List invoices with optional filters. You can filter by reference, year and use pagination with from and limit parameters.
List all mandates for a specific customer. Mandates represent payment authorizations for recurring charges. This endpoint returns all mandate records associated with a customer, showing their status (valid, invalid, pending), payment method, and consumer details. Useful for managing recurring payment authorizations and checking which mandates are available for charging.
Retrieve a list of payment links.
Search for paymentlinks within a specific timeframe by providing the starting date and the ending date. The results includes payments ids and their descriptions.
List all enabled payment methods for the profile. This endpoint returns only methods that are currently enabled and available for use. The results are not paginated.
Retrieve a list of payments for a customer.
Retrieve a list of payments for a given payment link.
List payments with optional filters.
Search for payments within a specific timeframe by providing the starting date and the ending date. The results includes payments ids and their descriptions.
List all captures included in a specific settlement. Captures are used for capture-based payment methods like Klarna Pay Later and Klarna Slice It. This shows which authorized payments were actually captured and included in the settlement payout. You can optionally embed the full payment details for each capture.
List all chargebacks included in a specific settlement. Chargebacks are disputed payments that customers have contested with their bank. Like refunds, chargebacks are subtracted from the settlement amount. This shows all chargeback transactions that reduced the payout for this settlement. You can optionally embed the full payment details for each chargeback.
List all payments included in a specific settlement. This shows which successful payments contributed to the settlement amount. Use this to see a detailed breakdown of all payment transactions that are part of a particular payout. Note: For capture-based payment methods like Klarna, use ListSettlementCaptures instead.
List all refunds included in a specific settlement. Refunds are subtracted from the total settlement amount since they represent money returned to customers. This shows all refund transactions that reduced the payout amount for this settlement. You can optionally embed the full payment details for each refund.
List all settlements available to your account. This endpoint returns a paginated list of all settlements, which represent the periodic payouts to your bank account. Each settlement includes the total amount of successful payments minus refunds and fees for a specific period. You can filter by balance, year/month, or currencies.
List all payments that were automatically created by a specific subscription. Shows the payment history for a subscription, including successful payments, failed payments, and pending payments. Each payment includes its ID, status, amount, and creation date. Useful for tracking subscription payment history, identifying failed charges, and customer support inquiries.
List all physical point-of-sale terminals available to your account. This endpoint returns a paginated list of all terminals registered to your Mollie account, including their status, brand, model, and other details. Terminals are physical devices used for accepting in-person card payments.
List all webhooks with optional filters. You can filter by event types and use pagination with from and limit parameters.
Revoke (cancel) a mandate to prevent future recurring charges using this authorization. Once revoked, the mandate cannot be used for new payments and the action cannot be undone. The customer will need to provide a new authorization if you want to charge them again in the future. Use this when a customer cancels their subscription or requests to stop recurring payments. This endpoint requires the 'mandates.write' scope.
Search for customers by name
Search for payments by description. This can be used to search for payments using a partial description.
Test a webhook by triggering a test ping. This sends a test event to your webhook URL to verify it's working correctly. The webhook will receive a sample POST request.
Updates an existing customer.
Update an existing subscription's settings. You can change the amount, interval, description, number of remaining payments, start date, webhook URL, or mandate. Changes take effect from the next scheduled payment. This is useful for price changes, interval modifications, or updating payment methods. This endpoint requires the 'subscriptions.write' scope.
Update an existing webhook. You can change the URL, name, or event types that the webhook subscribes to.
Fetch and parse documentation from a given URL or local file. Use this tool after list_doc_sources to: 1. First fetch the llms.txt file from a documentation source 2. Analyze the URLs listed in the llms.txt file 3. Then fetch specific documentation pages relevant to the user's question Args: url: The URL to fetch documentation from. Returns: The fetched documentation content converted to markdown, or an error message if the request fails or the URL is not from an allowed domain.
List all available documentation sources. This is the first tool you should call in the documentation workflow. It provides URLs to llms.txt files or local file paths that the user has made available. Returns: A string containing a formatted list of documentation sources with their URLs or file paths