bepaid-mcp
This MCP server lets you query, export, and create bePaid payment transactions and payment links, with optional roster-based payer/group management.
List transactions for a period (compact rows + totals, filter by status, date type, payment methods).
Look up a transaction by uid, tracking_id, or order_id, including live status and test transactions.
Export all transactions of a period to XLSX or CSV with fees, payouts, payer, card, and card-issuing country.
Create one-off payment links with amount, description, tracking_id, and required payer fields.
If a roster workbook is configured, use roster tools to list groups, find payers, report payments per group, export group reports, and create payer-specific payment links.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bepaid-mcp export last month's transactions to XLSX"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bepaid-mcp
MCP server for the bePaid payment gateway:
Unofficial. A community project, not affiliated with or endorsed by bePaid. It uses the public bePaid APIs with your own shop credentials.
Transactions — list, look up and export transactions of a period (paginated report API) with fees, payouts, payer and card data, and the country of the card-issuing bank (domestic / foreign).
Payment links — one-off checkout pages with your own
tracking_idand required payer fields.Roster module (optional) — with a groups/payers workbook: payments per group and payer, per-payer payment links whose
tracking_ididentifies group, meeting and payer.
Tools
Always available:
Tool | Purpose |
| Transactions for a period (compact rows + totals) |
| Lookup by |
| All transactions of a period to a new XLSX (summary + transactions) or CSV |
| One-off payment link: amount, description, |
Registered only when ROSTER_XLSX_PATH is set:
Tool | Purpose |
| Groups from the roster workbook |
| Payer lookup by id, email, phone or name |
| Payments per group → payer, plus |
| Same report written to a new XLSX/CSV file |
| Payment link for a roster payer (prefilled payer, exact matching) |
Related MCP server: paystack-mcp-server
Setup
Getting the shop ID / secret key and the first test run: docs/credentials.md.
Requires Node.js 20+. Register with Claude Code (runs the published package via npx):
claude mcp add bepaid --scope user \
-e BEPAID_SHOP_ID=... -e BEPAID_SECRET_KEY=... \
-- npx -y bepaid-mcpOther MCP clients (Claude Desktop, Cursor, ...):
{
"mcpServers": {
"bepaid": {
"command": "npx",
"args": ["-y", "bepaid-mcp"],
"env": { "BEPAID_SHOP_ID": "...", "BEPAID_SECRET_KEY": "..." }
}
}
}Variable | Description |
| Shop credentials (HTTP Basic auth for all bePaid APIs) |
|
|
| Time zone for report periods (default |
| Optional redirect after checkout |
| Optional roster workbook (read-only); enables the |
| Comma-separated substrings identifying bePaid payment URLs in the roster |
| Output folder for exports (default |
|
|
From a local checkout:
npm install && npm run build
cp .env.example .env # fill in; npm start / npm run inspect read it
claude mcp add bepaid -- node --env-file=/absolute/path/.env /absolute/path/dist/index.jsRoster workbook format
Sheet
Groups: columnsГруппа,Основная локация,Тип, optionalПрограмма— the payment description bePaid shows for the group's payments (e.g.Основы терапии; quotes and case are ignored).One sheet per group: cell
B1holds the group code; a header row (within the first 10 rows) starts with the payer columnПлательщик(also accepted:Обучающийся,Payer). Columns are located by header name:First Name + Last Name,Имя Фамилия Отчество,Email,Phone,Телеграм ник,Способ оплаты.Optional sheet
Модули— one row per module, header in row 1:Группа
Встреча
Дата
Цена
Валюта
Альфа-25.1
1
14.09.2026
550
BYN
Группаis the group code (as inB1of the group sheet);Датаa date cell orDD.MM.YYYY;Валютаdefaults to BYN. Unreadable rows are listed as warnings byroster_list_groups.Optional sheet
Ручные сопоставления— assignments for payments that cannot be matched automatically (ERIP, a relative's card), header in row 1:UID транзакции
Группа
Плательщик
Встреча
Комментарий
12345-abcdef0123
Альфа-25.1
Анна Иванова
3
ЕРИП
Copy
UID транзакцииfrom the export.Плательщикaccepts a name, email, phone or roster id.
Payment matching
Manual assignment (
Ручные сопоставления) by transaction UID.tracking_idof links created by this server (exact group, meeting and payer).Payment description → only groups with that
Программа. A description no group has (e.g. an individual consultation) goes to «Другие программы»; groups without aПрограммаvalue always stay candidates.Payer email → phone → name (first + last name, any order, Cyrillic or Latin) → name allowing Belarusian passport spellings (Volha = Ольга, Aliaksandra = Александра; reported as
name_fuzzy— worth a glance).If the payer studies in several groups:
price — the amount must equal the group's module price or a multiple of it (several modules paid at once). Exactly one fitting group wins; none fitting → left for review.
date — if several groups fit the price, the group with a module date nearest to the payment date wins.
Otherwise (no data, equal distance) the payment is listed as
ambiguousfor manual review.
The report column «Группа выбрана по» shows which rule decided.
Payment origin
Every payment carries the country of the card-issuing bank (issuer_country from bePaid; ERIP is always BY).
Reports total domestic / foreign payments, foreign ones per country and per group, and the export has a sheet
«Иностранные платежи» with all foreign payments (matched or not) for declaring them to the bank.
Publishing
npm version patch # or minor / major
npm publish # prepublishOnly builds and runs the testsDevelopment
npm test # vitest
npx vitest run test/report.test.ts -t "ambiguous" # single file / test
npm run typecheck
npm run inspect # MCP Inspector against dist/Testing payments: in test mode use card 4200000000000000 (success) or 4005550000000019 (failure).
License
MIT
Available Tools
4 toolsbepaid_create_payment_linkCreate bePaid payment linkA
Creates a one-off bePaid payment page (checkout token) and returns its URL. Links are test payments unless the server runs with BEPAID_TEST_MODE=false.
Inputs: amount (required), description (required), test, currency, +6 more.
bepaid_export_transactionsExport bePaid transactionsA
Writes all transactions of a period to a new XLSX (summary + transactions sheets) or CSV file: amounts, fees, payouts, payer, card, issuing bank country (domestic/foreign). Totals cover successful payments.
Inputs: to (required), from (required), format, status, +3 more.
bepaid_get_transactionGet bePaid transactionARead-only
Looks up a transaction by its uid, or all transactions with a given tracking_id. Also finds test transactions, which the report API does not return. With a roster configured, shows the matched group/payer.
Inputs: uid, tracking_id.
bepaid_list_transactionsList bePaid transactionsARead-only
Lists bePaid transactions for a period (paginated report API) as compact rows. Test transactions are not included by bePaid.
Inputs: to (required), from (required), limit, status, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a clearly distinct action: listing a period's transactions, looking up a single transaction (or by tracking_id), exporting to a file, and creating a payment link. The list/get distinction is standard and well-explained, leaving no realistic misselection risk.
All four names share the bepaid_ prefix and follow a clean verb_noun pattern (list_transactions, get_transaction, export_transactions, create_payment_link). No style mixing or vague verbs.
Four tools is a tight, focused set for transaction lookup/export plus payment-link creation, with each tool earning its place. It sits at the low end of the ideal 3-15 range, so slightly thin but not mismatched.
The read/reporting surface is solid (list, get, export) and creation of a payment link is covered, but there are no write/lifecycle operations such as refunds, payment cancellation, or status/webhook management. Notable gaps exist for an agent handling full payment workflows.
Maintenance
Related MCP Connectors
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Self-facilitated x402/MCP payments for hosted endpoints, rail proofs, receipts, and agents.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
Payments MCP: self-serve merchant key, PayNow + PayPal checkouts.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with the South African PayFast payment gateway to manage transactions, subscriptions, and refunds. It allows users to create payments, query transaction statuses, and check settlement balances through the MCP protocol.816 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Paystack via MCP tools to get total transactions, create checkout links, and verify transactions.3,749 npm4MIT

AgentTax MCP Serverofficial
AlicenseAqualityCmaintenanceEnables MCP tool developers and AI agents to track payments, calculate sales tax liability, and ensure tax compliance across US jurisdictions.6144 npmMIT- AlicenseBqualityDmaintenanceEnables support agents to look up customer account details and billing or incident information through two read-only MCP tools for triage workflows.2MIT