Bayarcash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAYARCASH_SANDBOX | No | Use sandbox (true) or production (false) | true |
| BAYARCASH_API_TOKEN | Yes | Your API token from console.bayar.cash | |
| BAYARCASH_API_SECRET_KEY | Yes | Your API secret key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_payment_intentA | Create a new payment intent for processing payments through Bayarcash. Returns payment intent ID in response. WORKFLOW: 1) If user did not provide payer_email, call list_transactions (per_page=1) to get latest email and ask: "Use email from last payment: {email}?" 2) If user did not provide portal_key, call get_portals and ask user to select. 3) If user did not specify payment channel, call get_payment_channels and ask user to select. 4) Ask if they want to provide phone number (optional). IMPORTANT: Store the returned "id" field (e.g., pi_pGwAaq) to check payment status later. |
| get_payment_intentB | Get payment intent details and status by payment intent ID. Returns comprehensive payment history including all attempts. |
| get_transactionC | Get transaction details by transaction ID |
| get_transaction_by_orderC | Get transaction details by order number |
| list_transactionsB | List all transactions with optional filters. If you have payer_email from previous payment creation, ask user: "Filter by email from last payment: {email}?" |
| get_portalsB | Get list of available payment portals |
| get_payment_channelsB | Get list of available payment channels |
| get_fpx_banksB | Get list of FPX banks for online banking payments |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Payment Portals | List of all available payment portals and their configurations |
| Payment Channels | List of all available payment channels across all portals |
| FPX Banks | List of FPX banks available for online banking payments |
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as create_payment_intent for initiating payments and get_fpx_banks for retrieving bank options. However, get_transaction and get_transaction_by_order could cause confusion as they both retrieve transaction details but by different identifiers, potentially leading to misselection if the agent is unclear about the available IDs.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_payment_intent, get_fpx_banks, and list_transactions. This predictability makes it easy for an agent to understand and navigate the tool set without ambiguity in naming conventions.
With 8 tools, the server is well-scoped for payment processing, covering key operations like creating intents, retrieving details, and listing transactions. Each tool serves a clear purpose, and the count aligns with typical domain needs without being overly sparse or bloated.
The tool set provides strong coverage for payment processing, including creation, status checks, and transaction retrieval. A minor gap exists in the lack of update or delete operations for payment intents or transactions, which might limit agent flexibility in handling errors or modifications, but core workflows are well-supported.