Japan Payments MCP — 日本で AI エージェントが決済リンクを作れる MCP サーバー

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

{
  "mcpServers": {
    "japan-payments": {
      "type": "http",
      "url": "https://mcp-jp.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

Deploy with Vercel

git clone https://github.com/junter1989k-ai/japan-payments-mcp && cd japan-payments-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Live · MCP endpoint: https://mcp-jp.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/japan-payments-mcp · Sister servers: Taiwan · Korea · Indonesia · India

English below. / 日本語は下記の通り。

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Japan:

🏪 コンビニ決済 (konbini) — the payment rail Japan actually uses; buyer gets a code and pays at the convenience store
💳 Credit card / PayPay / bank transfer / Pay-easy / LINE Pay / Merpay / au PAY / Rakuten Pay
🔍 Payment status check — pull-based, no webhook needed

v0.1 routes through KOMOJU, a Japanese payment gateway with a hosted checkout page. The provider registry is built for aggregation — more Japanese gateways join behind the same tools.

⚖️ Stateless translation layer: funds always flow buyer → KOMOJU → merchant directly. This server never holds, moves, or stores funds or credentials — no database at all.

Why this exists

Japanese payment rails — especially konbini — are built for humans clicking through web pages. An AI agent has no agent-ready API for "let my customer pay at 7-Eleven". This MCP server translates that flow into tools an agent can call.

Quick start

MCP endpoint: https://mcp-jp.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC)

Add the server URL in any remote-MCP client (Claude Desktop / Claude Code / Cursor…), then send your KOMOJU key as a header on each request:

Header	Value
`x-komoju-secret-key`	Your KOMOJU secret key. `sk_test_...` = test mode (no real money, free from the KOMOJU dashboard after switching to Test mode); `sk_live_...` = production.

No public demo key exists for KOMOJU, so bring your own — a test-mode key takes a minute to get and never moves real money.

Tools

Tool	What it does
`create_payment_link`	Create a JPY hosted-checkout link (konbini / card / PayPay / …). Returns the URL the buyer opens.
`query_payment_status`	Check whether a session has been paid (`captured` / `authorized`).

Develop

node test/serve.js      # local server (http://localhost:3211/mcp)
node test/e2e.js        # protocol + validation suite (probes real KOMOJU auth errors)

Zero runtime dependencies; Node ≥ 18.

English summary

Remote MCP server for Japan payments: konbini (コンビニ決済), credit cards, PayPay, bank transfer and more, via KOMOJU's hosted checkout. Bring-your-own credentials (x-komoju-secret-key), stateless, never touches funds, MIT-licensed, zero dependencies. Endpoint: https://mcp-jp.wishpool.app/mcp.

Part of a family: Taiwan Payments MCP covers Taiwan (ECPay 綠界 / NewebPay 藍新 + government e-invoices 電子發票) · Korea Payments MCP covers Korea (Toss Payments — cards / KakaoPay·NaverPay / 가상계좌) · Indonesia Payments MCP covers Indonesia (Midtrans Snap — GoPay / QRIS / Alfamart) · India Payments MCP covers India (Razorpay Payment Links — UPI / cards).

app.wishpool/japan-payments-mcp