bepaid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPORT_DIR | No | Output folder for exports (default `./exports`) | |
| BEPAID_SHOP_ID | Yes | Shop ID credential (HTTP Basic auth for all bePaid APIs) | |
| EXPORT_LANGUAGE | No | `ru` (default) or `en` — headers of `bepaid_export_transactions` | |
| BEPAID_TEST_MODE | No | `true` by default — links are test payments; set `false` for real payments | |
| BEPAID_TIME_ZONE | No | Time zone for report periods (default `Europe/Minsk`) | |
| ROSTER_XLSX_PATH | No | Optional roster workbook (read-only); enables the `roster_*` tools | |
| BEPAID_RETURN_URL | No | Optional redirect after checkout | |
| BEPAID_SECRET_KEY | Yes | Shop secret key credential (HTTP Basic auth for all bePaid APIs) | |
| ROSTER_BEPAID_URL_MARKERS | No | Comma-separated substrings identifying bePaid payment URLs in the roster |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bepaid_list_transactionsA | Lists bePaid transactions for a period (paginated report API) as compact rows. Test transactions are not included by bePaid. |
| bepaid_get_transactionA | 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. |
| bepaid_export_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. |
| bepaid_create_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.