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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/khairulimran-97/bayarcash-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server