W

WayForPay, inside Claude & Cursor

Ask your AI for merchant balance, transactions, invoices, and refunds - and let it act with gated mutations. Model Context Protocol, installed with one copy-paste.

npmMIT licenseClaudeCursor5 toolsopen source
WayForPay MCP README tool table showing read and gated write operations
Product stance

Your keys never touch our servers

WayForPay credentials are read from your local client config and sent only to WayForPay APIs. Mutations should be gated and require explicit approval.

What it does

Focused behavior, no theatre

read

get_merchant_balance

Current available balance.

read

list_transactions

Filterable payment history.

read

list_regular_payments

Recurring and subscription payments.

gated

create_invoice

Generate a payment link.

gated

refund

Refund a transaction.

gated

settle

Settle a held payment.

Install

One command, then review the app docs

npx @rmarinsky/wayforpay-mcp

For MCP servers, keep credentials in your local client config. For Mac apps, use the latest release notes as the source of truth for requirements.

FAQ

Practical details

Which clients are supported?

Any MCP client that accepts a standard mcpServers config, including Claude Desktop, Claude Code, Cursor, and VS Code-style clients.

Are my payment credentials safe?

Keys are read from local configuration. Every mutation should require explicit confirmation.

How do I keep it updated?

npx fetches the latest published version on launch, unless your client pins a package version.

Let your AI talk to WayForPay