khqrpay-mcp
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., "@khqrpay-mcp create a test KHQR payment for $1 and simulate it as paid"
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.
khqrpay-mcp
A local MCP server for KHQRPay, the KHQR payment gateway and API for Cambodia. It lets an AI coding tool create and check KHQR test payments, read payments, show your plan's usage and check webhook signatures while it builds your integration. It runs on your own machine, with your own key.
What it can do
Tool | What it does | Key |
| Creates a test payment: a KHQR no bank will pay, with a hosted checkout page | Test only |
| Moves a test payment to scanned, paid, expired or failed; your test webhook endpoints get the events | Test only |
| Reads one payment: status, amounts, expiry, whether it was paid late | Test, or live with opt-in |
| Lists payments, newest first, a page at a time | Test, or live with opt-in |
| Shows your plan's paid transactions used and left | Test, or live with opt-in |
| Checks an | Runs locally |
Related MCP server: @moncashconnect/mcp
Safe by default
Test keys do everything. Use a
kp_test_key: test payments never reach a bank and never count toward your plan.Live keys never create or change anything. With a
kp_live_key,create_test_paymentandsimulate_test_paymentrefuse, and the read tools work only if you setKHQRPAY_MCP_LIVE_READS=1.Secrets stay in the environment. Keys are read from environment variables and never printed. The webhook signing secret is never a tool argument, and
check_webhook_signaturenever shows the right signature.No polling. Reads count toward your account's daily read allowance, so the read tools tell the model to read once, not in a loop. Your own app should follow payments with webhooks.
Set up
You need Node.js 18 or newer and a test key from the KHQRPay dashboard (API keys, with the page set to Test).
Claude Code
claude mcp add khqrpay -e KHQRPAY_SECRET_KEY=kp_test_… -- npx -y khqrpay-mcpClaude Desktop, Cursor and other clients that read an mcpServers file (claude_desktop_config.json, .cursor/mcp.json):
{
"mcpServers": {
"khqrpay": {
"command": "npx",
"args": ["-y", "khqrpay-mcp"],
"env": { "KHQRPAY_SECRET_KEY": "kp_test_…" }
}
}
}Add "KHQRPAY_WEBHOOK_SECRET": "whsec_…" to env to use check_webhook_signature with your test endpoint's signing secret.
Environment
Variable | What it's for |
| Your KHQRPay key. |
| Set to |
| A webhook endpoint's signing secret, for |
| Another KHQRPay address, for testing. Must be https, or http on localhost |
Learn more
KHQRPay docs: payments, webhooks, test mode and going live.
The AI brief: every docs page in one file, for your coding tool's context.
License
MIT
Available Tools
6 toolscheck_webhook_signatureCheck a webhook signatureARead-only
Checks an X-KHQRPay-Signature header against a webhook's raw body, with the signing secret from this server's KHQRPAY_WEBHOOK_SECRET (the secret is never an argument and never shown). Says why a check fails: a malformed header, a timestamp more than 5 minutes off, or a mismatch. Runs on this machine; nothing is sent anywhere.
Inputs: raw_body (required), signature_header (required).
create_test_paymentCreate a test paymentA
Creates a KHQRPay test payment: a KHQR that no bank will pay, with a hosted checkout page. Only with a kp_test_ key: this server never creates live payments. Returns the payment, including checkout_url and expires_at. Move it with simulate_test_payment; the store's test webhook endpoints get the events.
Inputs: amount (required), currency, metadata, reference_id.
get_paymentGet a paymentARead-only
Reads one payment by its id: status (pending, scanned, paid, expired or failed), amounts, expiry, and whether it was paid late. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.
Inputs: id (required).
get_usageGet plan usageARead-only
Shows the account's plan, its paid transactions used and left this period, and when the period ends. Only paid live payments count; test payments never do.
Inputs: no named parameters.
list_paymentsList paymentsARead-only
Lists the store's payments in the key's mode, newest first, one page at a time; each leaves out metadata, which get_payment returns. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.
Inputs: limit, cursor, status.
simulate_test_paymentSimulate a test paymentAIdempotent
Moves a test payment to scanned, paid, expired or failed, as if the customer and the bank had acted, and the store's test webhook endpoints get the matching event. Test payments only. To try a late payment, simulate expired and then paid. A status the payment can't move to changes nothing.
Inputs: id (required), status (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: usage/limits (get_usage), creation (create_test_payment), state transition (simulate_test_payment), single read (get_payment), bulk read (list_payments), and webhook verification (check_webhook_signature). The only near-neighbors, get_payment vs list_payments and create_test_payment vs simulate_test_payment, are explicitly differentiated by 'one payment' vs 'one page' and 'create' vs 'move' language.
All six tools follow a uniform snake_case verb_noun pattern (get_, create_, simulate_, list_, check_). The shared test_payment suffix groups related tools rather than creating inconsistency.
Six tools is well-scoped for a test-only payment API: usage, create, simulate, get, list, and signature check each cover a distinct step with no filler. Nothing feels padded or missing at the count level.
The test-payment lifecycle is closed: create -> simulate (including expired-then-paid for late payments) -> get/list -> verify webhook signature, plus account usage. Minor gaps remain: no refund/cancel operation, no webhook endpoint registration or event listing, and live payments are excluded by design.
Maintenance
Related MCP Connectors
Email inboxes, webhooks, mock APIs, 2FA codes, approvals and 170 tools for AI agents.
Give your AI agents trusted access to the full Postman platform.
Connect AI to store orders, products and inventory with scoped access and human approvals.
Vietnam payments for AI agents — MoMo wallet QR, ATM, cards. Zero-setup sandbox. Never holds funds.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables AI assistants to create payment links, invoices, and read order/balance status for Tegro.money payment shops, with safe read-and-collect-only access.610 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to interact with MonCashConnect payment data read-only, including checking balances, listing transactions, and viewing payment details, without moving money.5 npmMIT

Alternative Payments MCPofficial
AlicenseNot gradedqualityCmaintenanceProvides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect BLMPay balances, payments, payouts, webhooks, and API capabilities through MCP tools, with write/financial tools disabled by default for security.MIT