Saudi Arabia Payments MCP — let AI agents accept payments in Saudi Arabia

Use it in 60 seconds

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

{
  "mcpServers": {
    "saudi-arabia-payments": {
      "type": "http",
      "url": "https://mcp-sa.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:

git clone https://github.com/junter1989k-ai/saudi-arabia-payments-mcp && cd saudi-arabia-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-sa.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/saudi-arabia-payments-mcp · Part of a 30-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Saudi Arabia: mada (the Saudi debit network), Apple Pay, cards, STC Pay — whatever is enabled on the Tap account — via Tap Payments's hosted checkout.

⚖️ Stateless translation layer: funds always flow buyer → Tap Payments → merchant directly. Never holds funds or stores credentials — no database at all.

Related MCP server: app.wishpool/egypt-payments-mcp

Quick start

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

Tools

Develop

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

Zero runtime dependencies; Node ≥ 18. MIT license.