MCP for PayPay (Japan's QR wallet): QR codes, payments, refunds, cancels. Bilingual JP/EN.
Most payments and commerce work still happens through a UI a human drives. Paypay MCP server moves it into the conversation instead. MCP for PayPay (Japan's QR wallet): QR codes, payments, refunds, cancels. Bilingual JP/EN.
Model Context Protocol server for the PayPay Open Payment API.
The server publishes 7 tools. What each one is for:
create_qr_code — Create a dynamic PayPay QR code. Returns the payment URL, deeplink, and a rendered PNGget_payment_details — Fetch the current status of a paymentwait_for_payment — Poll until a payment reaches a terminal statedelete_qr_code — Invalidate a QR code before paymentrefund_payment — Full or partial refund. Disabled unless PAYPAY_ENABLE_REFUNDS=true.cancel_payment — Cancel a payment when its state is unclear (timeout or error). Disabled unless PAYPAY_ENABLE_CANCELS=true.Cursor — Add to ~/.cursor/mcp.json with the same shape as Claude Desktoppaypay-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: PAYPAY_API_KEY, PAYPAY_API_SECRET, PAYPAY_MERCHANT_ID, PAYPAY_ENV, MCP_HTTP_HOST, MCP_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Paypay's toolset — create_qr_code, get_payment_details, wait_for_payment and 4 more — is a fair guide to whether it matches your workflow. It is maintained by mrslbt; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_qr_code | Create a dynamic PayPay QR code. Returns the payment URL, deeplink, and a rendered PNG. |
| get_payment_details | Fetch the current status of a payment. |
| wait_for_payment | Poll until a payment reaches a terminal state. |
| delete_qr_code | Invalidate a QR code before payment. |
| refund_payment | Full or partial refund. **Disabled unless PAYPAY_ENABLE_REFUNDS=true.** |
| cancel_payment | Cancel a payment when its state is unclear (timeout or error). **Disabled unless PAYPAY_ENABLE_CANCELS=true.** |
| Cursor | Add to ~/.cursor/mcp.json with the same shape as Claude Desktop. |
{
"mcpServers": {
"paypay": {
"command": "npx",
"args": ["-y", "paypay-mcp"],
"env": {
"PAYPAY_API_KEY": "your-value",
"PAYPAY_API_SECRET": "your-value",
"PAYPAY_MERCHANT_ID": "your-value",
"PAYPAY_ENV": "your-value",
"MCP_HTTP_HOST": "your-value",
"MCP_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PAYPAY_API_KEY | Credential the server authenticates with. | Yes |
| PAYPAY_API_SECRET | Credential the server authenticates with. | Yes |
| PAYPAY_MERCHANT_ID | Configuration value read at startup. | Optional |
| PAYPAY_ENV | Configuration value read at startup. | Optional |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.