Japan Payments MCP

What is Japan Payments MCP?

A remote Model Context Protocol (MCP) server that lets AI agents create payment links and check payment status for Japanese payment rails — konbini (コンビニ決済), credit cards, PayPay, bank transfer, Pay-easy, LINE Pay, Merpay, au PAY, and Rakuten Pay. It works as a stateless translation layer routing through KOMOJU, a Japanese payment gateway with a hosted checkout page. The server is designed for developers building agentic applications that need to accept payments in Japan.

How to use Japan Payments MCP?

Add the endpoint https://mcp-jp.wishpool.app/mcp in any remote-MCP client (Claude Desktop, Claude Code, Cursor). On each request, send your KOMOJU secret key as the header x-komoju-secret-key. Two tools are available: create_payment_link (creates a JPY hosted-checkout link) and query_payment_status (checks if a session is paid).

Key features of Japan Payments MCP

• Accept payments via konbini (convenience store) and 10+ Japanese methods
• Pull-based payment status check — no webhook required
• Stateless: never holds, moves, or stores funds or credentials
• Bring your own KOMOJU secret key (test or live)
• Zero runtime dependencies; Node ≥ 18 for local development
• Remote MCP endpoint compatible with any MCP client

Use cases of Japan Payments MCP

• AI assistants that need to generate a payment link for a customer to pay at a Japanese convenience store
• Chatbot agents that collect payments via credit card or PayPay in yen
• Automated workflows that verify payment completion without polling a third-party service
• Multi-country payment scenarios using the sister servers for Taiwan, Korea, Indonesia, and India

FAQ from Japan Payments MCP

What does Japan Payments MCP actually do?

It provides two tools for AI agents: create a Japanese hosted-checkout payment link and check whether that session has been paid (captured or authorized). Funds flow directly from buyer to merchant via KOMOJU; the server never handles money.

How do I get credentials?

You need your own KOMOJU secret key. A test-mode key (sk_test_...) is free from the KOMOJU dashboard after switching to Test mode, and never moves real money. A production key (sk_live_...) is for live payments. There is no public demo key.

Does this server store any data?

No. It is a stateless translation layer with no database. It never holds, moves, or stores funds, credentials, or any other sensitive data.

How do I check if a payment succeeded?

Call the query_payment_status tool with the session identifier. It returns the current status (e.g., captured or authorized). The check is pull-based — no webhook configuration is needed.

What runtime does the server require?

The remote endpoint is always available. For local development, you need Node.js ≥ 18. The server has zero runtime dependencies.