Mollie Agent Skills

⚠️

You are responsible for all actions performed within your Mollie account by any AI tool that you connect, authorize or configure. Actions taken by an AI tool using your authorized access are treated in the same way as actions taken by you in the Mollie web app or using the API.
You are responsible for the permissions and authority you grant to the tool.

Mollie is not responsible for the decisions, outputs, errors or actions done by third-party AI tools, models or services that you choose to connect to your account.

What are Agent Skills?

If you use an AI coding assistant - Claude Code, Cursor, Codex or Gemini CLI - to build something with Mollie, Agent Skills are pre-packaged know-how packages of instructions that switch on automatically the moment you start working with Mollie.
It gives your AI assistant built-in knowledge of the right approach, the current SDK options and the common mistakes to avoid - so you don't need to navigate our API documentation to start.

You don't have to ask for a skill by name - your AI assistant picks the right one based on what you're trying to do automatically.

Before you start

You'll need a Mollie Advanced access token with the profile.read scope. Set it as an environment variable before installing:

export MOLLIE_API_ADVANCED_ACCESS_TOKEN="your_token_here"

Claude Code

# 1. Add the Mollie plugin marketplace
claude plugin marketplace add mollie/ai

# 2. Install the plugin
claude plugin install mollie@mollie

Then run /reload-plugins to activate it without restarting.

Cursor

codex plugin add github:mollie/ai

Gemini CLI

gemini extensions install github:mollie/ai

The three skills

SkillUse it when you want toWhat it helps with
mollie-paymentsBuild a new integrationAccepting payments, setting up Mollie Connect for a platform or marketplace, recurring payments and subscriptions, refunds and captures, sales invoices and troubleshooting a stuck payment or missing webhook
mollie-upgradeUpdate or migrate existing codeUpgrading to a newer SDK version or moving off the older Orders API onto the current Payments API
mollie-agent-toolkitBuild your own AI agent that uses MollieChoosing the right building blocks and safety guardrails for your AI agent to check (or act on) Mollie data

What each skill actually does for you

SkillAction
mollie-payments

Asks a few quick questions before writing any code: are you building something new or fixing something that's broken? Do you sell directly or run a platform/marketplace on behalf of others? One-time payment or a subscription? etc. Then guides your AI to the right solution using the most current, appropriate Mollie SDK for your language.

It also knows Mollie's hard rules and won't let your AI skip them:
  • Never put an API key in your website's frontend code - only a profile ID belongs there.
  • Always confirm a payment's status through a webhook - never trust the redirect page alone.
  • Always respond to a webhook immediately, before doing anything else with it.
  • For actions that are difficult to reverse - a refund/capture/cancellation — stop and verify the details carefully before proceeding.
mollie-upgradeChecks what version of the Mollie SDK you're currently using, reads what's changed and walks you through the update instead of you having to work it out from a changelog yourself. If you're still using Mollie's older Orders API, it migrates you to the current Payments API step by step (these aren't a 1:1 rename — fields, capture behavior and cancellation work differently) and flags anything that needs a real decision instead of simply guessing.
mollie-agent-toolkit
For when you're building your own AI agent that can act on Mollie — not just answer questions about it.
Makes sure it's built safely from day one: give the agent only the permissions it actually needs and always require a person to approve anything that moves funds( e.g., a payment or a refund) before it actually happens. See this for the full list of building blocks this skill uses.
⚠️

An AI model can be misled into taking the wrong action by whatever text it's shown - a customer's message, a payment description etc. Skills won't let your AI treat "please ask the user first" as a good enough reason on its own; anything that moves funds needs a proper code-enforced check.

Also available


Did this page help you?