Bahrain Payments Mcp

What is Bahrain Payments MCP?

Bahrain Payments MCP is a remote MCP server that enables AI agents (Claude, ChatGPT, Cursor, etc.) to accept payments in Bahrain via Tap Payments’ hosted checkout. It supports Benefit (Bahraini debit network), cards, Apple Pay, and other methods enabled on the Tap account. The server acts as a stateless translation layer – funds flow directly from buyer to Tap Payments to the merchant, and it never holds funds or stores credentials.

How to use Bahrain Payments MCP?

To use the server, connect your AI agent to the MCP endpoint https://mcp-bh.wishpool.app/mcp and pass your Tap Payments secret key in the x-tap-secret-key header (free sk_test_ keys from businesses.tap.company; production uses sk_live_). Two tools are available: create_payment_link to generate a BHD hosted-checkout link and query_payment_status to pull-check if a payment has been marked paid. For local development, run node test/serve.js (server on port 3272) and node test/e2e.js for protocol validation.

Key features of Bahrain Payments MCP

• Accept payments via Benefit, cards, Apple Pay, and more.
• Stateless translation layer – no database, never holds funds.
• Provides two tools: create payment link and query payment status.
• Works with any AI agent supporting MCP (Claude, ChatGPT, Cursor).
• Part of a 71-country family of payment MCP servers.
• MIT licensed, zero runtime dependencies, Node ≥ 18.

Use cases of Bahrain Payments MCP

• An AI assistant generating checkout links for Bahraini customers.
• Automated payment status checks in conversational commerce flows.
• Integrating Tap Payments hosted checkout into agent-driven e-commerce.

FAQ from Bahrain Payments MCP

What payment methods are supported?

Benefit (Bahraini debit network), cards, Apple Pay, and any other method enabled on the linked Tap Payments account.

How does Bahrain Payments MCP handle funds and credentials?

It is a stateless translation layer: funds flow directly from buyer to Tap Payments to the merchant. It never holds funds, stores credentials, or runs a database.

What authentication is required?

Each request must include the x-tap-secret-key header with a valid Tap Payments secret key (free sk_test_ keys for testing, sk_live_ for production).

Can I develop and test locally?

Yes. Run node test/serve.js to start a local server at http://localhost:3272/mcp, and node test/e2e.js to run protocol and validation tests that probe real Tap Payments auth errors.

What are the runtime requirements?

Node.js version 18 or higher. The server has zero runtime dependencies.